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

Ability to use asset tags in rack view instead of device names #381

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

Originally created by @ingeba on GitHub (Aug 19, 2016).

For our DC's, the current solution of using names in the graphical overview of racks does not work too well:

  • Not all devices have any names beyond their asset tags.
  • Those devices that do have names, have FQDN's as names which exceed the width of the rack drawings, making the rack entries impossible to read. We have no good way of shortening these FQDNs to a length that would fit the rack drawings.

We may of course duplicate the asset tag in the name field, but then we are no longer able to find hardware given its currently assigned FQDN.

Instead we prefer to use asset tags in rack view but keep FQDN's as names for those devices that has it. All devices at our sites are regarded as assets and registered with a unique tag with reasonable length upon arrival, following the hardware to its death. We have made a small patch to Netbox to use asset tags instead of names in rack views and instead include the name with the other information given in the mouse-over hover bubble. We have also increased the maximum name size to support all our FQDN's.

Of course what suits us may not suit all, but having this as an option would be good for us and maybe others?

Originally created by @ingeba on GitHub (Aug 19, 2016). For our DC's, the current solution of using names in the graphical overview of racks does not work too well: - Not all devices have any names beyond their asset tags. - Those devices that do have names, have FQDN's as names which exceed the width of the rack drawings, making the rack entries impossible to read. We have no good way of shortening these FQDNs to a length that would fit the rack drawings. We may of course duplicate the asset tag in the name field, but then we are no longer able to find hardware given its currently assigned FQDN. Instead we prefer to use asset tags in rack view but keep FQDN's as names for those devices that has it. All devices at our sites are regarded as assets and registered with a unique tag with reasonable length upon arrival, following the hardware to its death. We have made a small patch to Netbox to use asset tags instead of names in rack views and instead include the name with the other information given in the mouse-over hover bubble. We have also increased the maximum name size to support all our FQDN's. Of course what suits us may not suit all, but having this as an option would be good for us and maybe others?
adam closed this issue 2025-12-29 16:21:29 +01:00
adam commented 2025-12-29 16:21:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 9, 2017):

This feature request hasn't gotten any traction in a year. I've added the asset tag to the pop-up bubble, which should be sufficient.

@jeremystretch commented on GitHub (Oct 9, 2017): This feature request hasn't gotten any traction in a year. I've added the asset tag to the pop-up bubble, which should be sufficient.
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
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#381
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?