-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Comments
@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. |
Closing as looks like non issue |
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.
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. |
Deployment Type
Self-hosted
NetBox Version
v4.0.7
Python Version
3.10
Steps to Reproduce
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.
The text was updated successfully, but these errors were encountered: