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

Add Status column to Module Bays tables #7596

New Issue
Closed
opened 2025-12-29 20:25:51 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:25:51 +01:00
Owner
Copy Link

Originally created by @sleepinggenius2 on GitHub (Feb 2, 2023).

Originally assigned to: @abhi1693 on GitHub.

NetBox version

v3.4.3

Feature type

Change to existing functionality

Proposed functionality

A Status field was added to Modules in #10371. I am proposing making that field available as a column on the Module Bays tables (full list and tab under a device). There is existing precedent for Module fields to be added as column options for those tables, like Serial number and Asset tag. I would additionally propose adding that column as one of the defaults on those tables, as was done for the Modules table.

Use case

Adding this as a table column would increase its visibility and make it easier to understand at a glance the status of all the modules in a shelf. Currently, a user would need to click into a given module in the list to see its status, which becomes cumbersome on a shelf with many modules.

Database changes

None

External dependencies

None

Originally created by @sleepinggenius2 on GitHub (Feb 2, 2023). Originally assigned to: @abhi1693 on GitHub. ### NetBox version v3.4.3 ### Feature type Change to existing functionality ### Proposed functionality A *Status* field was added to *Modules* in #10371. I am proposing making that field available as a column on the *Module Bays* tables (full list and tab under a device). There is existing precedent for *Module* fields to be added as column options for those tables, like *Serial number* and *Asset tag*. I would additionally propose adding that column as one of the defaults on those tables, as was done for the *Modules* table. ### Use case Adding this as a table column would increase its visibility and make it easier to understand at a glance the status of all the modules in a shelf. Currently, a user would need to click into a given module in the list to see its status, which becomes cumbersome on a shelf with many modules. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:25:52 +01:00
adam closed this issue 2025-12-29 20:25:52 +01:00
adam commented 2025-12-29 20:25:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2023):

It should be straightforward to add the table column, however a solution will be needed to display the badge label color correctly.

@jeremystretch commented on GitHub (May 3, 2023): It should be straightforward to add the table column, however a solution will be needed to display the badge label color correctly.
adam commented 2025-12-29 20:25:52 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (May 3, 2023):

I'll take a stab at this.

@abhi1693 commented on GitHub (May 3, 2023): I'll take a stab at this.
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: accepted type: feature
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#7596
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?