starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Missing description for installed module in module bays list #9977

New Issue
Closed
opened 2025-12-29 21:25:09 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:25:09 +01:00
Owner
Copy Link

Originally created by @grbeneke on GitHub (Jul 12, 2024).

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.

Originally created by @grbeneke on GitHub (Jul 12, 2024). ### 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.
adam added the type: bugstatus: revisions needed labels 2025-12-29 21:25:09 +01:00
adam closed this issue 2025-12-29 21:25:09 +01:00
adam commented 2025-12-29 21:25:10 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 12, 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. 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 commented on GitHub (Jul 12, 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. 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. <img width="1137" alt="tmodulebay | NetBox 2024-07-12 16-58-16" src="https://github.com/user-attachments/assets/f42471ab-db93-4625-ae4d-bc45f7538514">
adam commented 2025-12-29 21:25:10 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 16, 2024):

Closing as looks like non issue

@arthanson commented on GitHub (Jul 16, 2024): Closing as looks like non issue
adam commented 2025-12-29 21:25:11 +01:00
Author
Owner
Copy Link

@grbeneke commented on GitHub (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.

@grbeneke commented on GitHub (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.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: revisions needed type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#9977
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?