Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing description for installed module in module bays list #16894

Closed
grbeneke opened this issue Jul 12, 2024 · 3 comments
Closed

Missing description for installed module in module bays list #16894

grbeneke opened this issue Jul 12, 2024 · 3 comments
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application

Comments

@grbeneke
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.0.7

Python Version

3.10

Steps to Reproduce

  1. Access the "Module Bays" tab of a device with module bays.
  2. Select the "Install module" option on an empty bay.
  3. Fill "Module Type" and "Description" fields and select "Create"
  4. After returning to the "Module Bay" page the "Description" column remains blank.

Expected Behavior

The "Description" column of the "Module Bays" list should show the description entered when installing the module.

Observed Behavior

The "Description" column of the "Module Bays" list is blank.

It appears that the value entered in the "Description" field is not lost and is visible when displaying the 'module' object individually. The value displayed in the "Module Bays" listing of the device appears to be derived from a "Description" field which exists separately in the 'module bay' object.

@grbeneke grbeneke added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jul 12, 2024
@arthanson arthanson assigned arthanson and unassigned DanSheps Jul 12, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available status: revisions needed This issue requires additional information to be actionable and removed status: needs triage This issue is awaiting triage by a maintainer status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Jul 12, 2024
@arthanson
Copy link
Collaborator

@grbeneke It looks like you are talking about the table field highlighted below? That is the description of the bay, not the child device. If you click the edit button to the right hand side and edit the bay you can set a description for the bay which is how I got "foo" to show there.

tmodulebay | NetBox 2024-07-12 16-58-16

@arthanson
Copy link
Collaborator

Closing as looks like non issue

@grbeneke
Copy link
Author

grbeneke commented Jul 19, 2024

@grbeneke It looks like you are talking about the table field highlighted below? That is the description of the bay, not the child device.

The screen-shot shows Device Bays - my bug report relates to Module Bays.

In the Module Bays tab - the two columns ahead of Description are Module Type (a field from the Module object) and Module Status (also a field from the Module object). This UI layout would intuitively lead the user to believe that the Description field also relates the the Module object.

If you click the edit button to the right hand side and edit the bay you can set a description for the bay which is how I got "foo" to show there.

I expect that most front-end users are editing the Description field like this to describe the function of the Module rather than the Bay. Describing the active installed component will typically have much more operational value than a description of the empty/underlying bay. It seems preferable to rather display the module description.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: revisions needed This issue requires additional information to be actionable type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

3 participants