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 device description columns to DeviceComponentsTable #11646

New Issue
Closed
opened 2025-12-29 21:48:01 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:48:01 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (Sep 24, 2025).

NetBox version

v4.4.0

Feature type

New functionality

Proposed functionality

I would also like to add an additional column for Device Description to all DeviceComponents tables.

And also add an Installed Device Description column to DeviceBay tables.

This does not add any database queries.

Use case

In our environment device descriptions are very important because most devices do not have a hostname. The name field is used only for devices which do have a meaningful hostname. For all the rest, we leave name blank to avoid uniqueness issues.

Here's an example to demonstrate the proposed functionality. We have two Adder ALIF4021T devices, which are mounted side by side in a single RU. To model this in Netbox, I have to model them as children, with a "generic 1U shelf" as the parent. The Device description field is how users tell the difference between the two devices on this shelf.
In this example, the Description column describes the bay itself, which is blank.
Device Description describes the shelf Device.
Installed Device Description describes the Device installed in the bay.

Image

Database changes

none

External dependencies

none

Originally created by @llamafilm on GitHub (Sep 24, 2025). ### NetBox version v4.4.0 ### Feature type New functionality ### Proposed functionality I would also like to add an additional column for `Device Description` to all DeviceComponents tables. And also add an `Installed Device Description` column to DeviceBay tables. This does not add any database queries. ### Use case In our environment device descriptions are very important because most devices do not have a hostname. The `name` field is used only for devices which do have a meaningful hostname. For all the rest, we leave `name` blank to avoid uniqueness issues. Here's an example to demonstrate the proposed functionality. We have two Adder ALIF4021T devices, which are mounted side by side in a single RU. To model this in Netbox, I have to model them as children, with a "generic 1U shelf" as the parent. The Device `description` field is how users tell the difference between the two devices on this shelf. In this example, the `Description` column describes the bay itself, which is blank. `Device Description` describes the shelf Device. `Installed Device Description` describes the Device installed in the bay. <img width="1057" height="393" alt="Image" src="https://github.com/user-attachments/assets/40fc140f-51cd-429d-a49f-0e063496846f" /> ### Database changes none ### External dependencies none
adam added the type: feature label 2025-12-29 21:48:01 +01:00
adam closed this issue 2025-12-29 21:48:01 +01:00
adam commented 2025-12-29 21:48:01 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 2, 2025):

Export templates are the right tool for customizing table output to include additional fields like this. Our view is that this leads to cluttered interfaces and performance issues. Going forward, we're going to be more cautious about accepting new columns that span relationships.

@jnovinger commented on GitHub (Oct 2, 2025): Export templates are the right tool for customizing table output to include additional fields like this. Our view is that this leads to cluttered interfaces and performance issues. Going forward, we're going to be more cautious about accepting new columns that span relationships.
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 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#11646
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?