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

Option not to display Asset Tag value appended to Device Name #10211

New Issue
Open
opened 2025-12-29 21:28:26 +01:00 by adam · 9 comments
adam commented 2025-12-29 21:28:26 +01:00
Owner
Copy Link

Originally created by @MattDRogers on GitHub (Sep 9, 2024).

NetBox version

v4.1.0

Feature type

Change to existing functionality

Proposed functionality

Either do not append the Asset Tag to the Device Name, or make it an option.

What it looks like now:
Screenshot 2024-09-09 092416
Screenshot 2024-09-09 092549
Screenshot 2024-09-09 092744

What I'd like the option to do:
Screenshot 2024-09-09 092416a
Screenshot 2024-09-09 092549a
Screenshot 2024-09-09 092744a

Use case

For display purposes, appending the Asset Tag to the Device Name uses up a lot of space--especially when one is looking at a list of cable connections. It makes for a more cluttered view (though I suppose this is subjective). Having the option to disable the parenthetical Asset Tag appearing next to the Device Name would streamline things visually, make tables display in a more easy-to-read fashion, and eliminate needless redundancy of information.

Database changes

I don't believe any database changes should be necessary, as these are two separately defined fields being displayed a certain way in the Web UI.

External dependencies

No external dependencies.

Originally created by @MattDRogers on GitHub (Sep 9, 2024). ### NetBox version v4.1.0 ### Feature type Change to existing functionality ### Proposed functionality Either do _not_ append the Asset Tag to the Device Name, or make it an _option_. **What it looks like now:** ![Screenshot 2024-09-09 092416](https://github.com/user-attachments/assets/934dba5e-3f29-4397-a097-661791d98c3d) ![Screenshot 2024-09-09 092549](https://github.com/user-attachments/assets/3e8a6469-39e9-4f06-a0cd-6f496b111fc0) ![Screenshot 2024-09-09 092744](https://github.com/user-attachments/assets/171a84cb-6502-4c80-b168-e217bfcca22d) **What I'd like the option to do:** ![Screenshot 2024-09-09 092416a](https://github.com/user-attachments/assets/44cea39a-af66-472f-902e-0758094c7459) ![Screenshot 2024-09-09 092549a](https://github.com/user-attachments/assets/b5c75507-2978-4965-8284-d7f76a4d6347) ![Screenshot 2024-09-09 092744a](https://github.com/user-attachments/assets/c6a11d8c-7438-4f80-86d5-9361589438e2) ### Use case For display purposes, appending the Asset Tag to the Device Name uses up a lot of space--especially when one is looking at a list of cable connections. It makes for a more cluttered view (though I suppose this is subjective). Having the option to disable the parenthetical Asset Tag appearing next to the Device Name would streamline things visually, make tables display in a more easy-to-read fashion, and eliminate needless redundancy of information. ### Database changes I don't believe any database changes should be necessary, as these are two separately defined fields being displayed a certain way in the Web UI. ### External dependencies No external dependencies.
adam commented 2025-12-29 21:28:26 +01:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 10, 2024):

I agree. Asset tag seems to be the only other field that gets added to a name if you have it filled in.
It was so cumbersome for our users we don't use the built-in asset tag field, instead opting to create a custom field for asset tag just so it won't get appended to the name.

@ghost commented on GitHub (Sep 10, 2024): I agree. Asset tag seems to be the only other field that gets added to a name if you have it filled in. It was so cumbersome for our users we don't use the built-in asset tag field, instead opting to create a custom field for asset tag just so it won't get appended to the name.
adam commented 2025-12-29 21:28:26 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Sep 10, 2024):

I like having it in selector fields but i dislike having it in most other places.

@ITJamie commented on GitHub (Sep 10, 2024): I like having it in selector fields but i dislike having it in most other places.
adam commented 2025-12-29 21:28:27 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 25, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 25, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:28:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 8, 2025):

This will probably involve removing the asset tag from the string returned by the model's __str__() method. However, IMO it make sense to still include the asset tag as part of the dropdown choices.

@jeremystretch commented on GitHub (May 8, 2025): This will probably involve removing the asset tag from the string returned by the model's `__str__()` method. However, IMO it make sense to still include the asset tag as part of the dropdown choices.
adam commented 2025-12-29 21:28:27 +01:00
Author
Owner
Copy Link

@MattDRogers commented on GitHub (May 9, 2025):

Agreed. Since the time I opened this FR, I have come to appreciate having the Asset Tag in dropdown lists. Thanks for looking at this.

@MattDRogers commented on GitHub (May 9, 2025): Agreed. Since the time I opened this FR, I have come to appreciate having the Asset Tag in dropdown lists. Thanks for looking at this.
adam commented 2025-12-29 21:28:27 +01:00
Author
Owner
Copy Link

@alisenkov commented on GitHub (May 30, 2025):

yes, we also need not showing asset tag in hostname

@alisenkov commented on GitHub (May 30, 2025): yes, we also need not showing asset tag in hostname
adam commented 2025-12-29 21:28:27 +01:00
Author
Owner
Copy Link

@alehaa commented on GitHub (Jul 15, 2025):

Do we need a user preference for this or could it be a configuration setting? If the latter, I’m willing to volunteer to create a PR.

@alehaa commented on GitHub (Jul 15, 2025): Do we need a user preference for this or could it be a configuration setting? If the latter, I’m willing to volunteer to create a PR.
adam commented 2025-12-29 21:28:28 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Sep 14, 2025):

Thanks, @alehaa! A global configuration setting seems like the right first step. If there’s interest in per‑user control later, we can track that as a separate feature request.
Are you still up for opening a PR?

@pheus commented on GitHub (Sep 14, 2025): Thanks, @alehaa! A global configuration setting seems like the right first step. If there’s interest in per‑user control later, we can track that as a separate feature request. Are you still up for opening a PR?
adam commented 2025-12-29 21:28:28 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 14, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 14, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
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 complexity: low netbox pending closure status: needs owner 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#10211
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?