starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Modules Display : Replace Netbox ID with AssetTag (if set) #10404

New Issue
Closed
opened 2025-12-29 21:31:00 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:31:00 +01:00
Owner
Copy Link

Originally created by @mathieued on GitHub (Oct 24, 2024).

NetBox version

v4.1.1

Feature type

Change to existing functionality

Triage priority

This is a very minor change

Proposed functionality

I don't know why the issue wasn't followed, but I'm creating this one for a topic exactly similar to the closed #10512

Unlike the previous issue, my point is mainly to point out an inconsistency in the Netbox UI that may confuse users.

Indeed, in my use case I use asset_tag for both Devices and Modules.

When an asset_tag is indicated at the Device level, it is displayed in the UI alongside the Device name. We therefore associate the asset_tag with the number in parentheses.

However, in the case of Modules, the number in parentheses represents the Netbox id and not the asset_tag, which can also be mentioned at the Module level.

In my opinion, it would make more sense to display the asset_tag between parentheses, to remain consistent with how Devices display is handled.

However, unlike what's said in #10512, I think it is still interesting to keep in display the module_bay name, because we can have several Modules of the same type associated with the same Device. And in this case, the name of the module_bay remains a means of identifying two different modules.

Use case

This feature would allow to bring more consistency to the information displayed to the user in the Netbox UI. And therefore, avoid misinterpretations.

Database changes

None that I'm aware of.

External dependencies

None that I'm aware of.

Originally created by @mathieued on GitHub (Oct 24, 2024). ### NetBox version v4.1.1 ### Feature type Change to existing functionality ### Triage priority This is a very minor change ### Proposed functionality I don't know why the issue wasn't followed, but I'm creating this one for a topic exactly similar to the closed #10512 Unlike the previous issue, my point is mainly to point out an inconsistency in the Netbox UI that may confuse users. Indeed, in my use case I use `asset_tag` for both *Devices* and *Modules*. When an `asset_tag` is indicated at the *Device* level, it is displayed in the UI alongside the *Device* `name`. We therefore associate the `asset_tag` with the number in parentheses. However, in the case of *Modules*, the number in parentheses represents the Netbox `id` and not the `asset_tag`, which can also be mentioned at the *Module* level. In my opinion, it would make more sense to display the `asset_tag` between parentheses, to remain consistent with how Devices `display` is handled. However, unlike what's said in #10512, I think it is still interesting to keep in `display` the `module_bay` name, because we can have several *Modules* of the same type associated with the same *Device*. And in this case, the name of the `module_bay` remains a means of identifying two different modules. ### Use case This feature would allow to bring more consistency to the information displayed to the user in the Netbox UI. And therefore, avoid misinterpretations. ### Database changes None that I'm aware of. ### External dependencies None that I'm aware of.
adam closed this issue 2025-12-29 21:31:01 +01:00
adam commented 2025-12-29 21:31:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 6, 2025):

Marking this as "needs owner" with the caveat that this should establish parity between the Device and Module models.

@jeremystretch commented on GitHub (Feb 6, 2025): Marking this as "needs owner" with the caveat that this should establish parity between the Device and Module models.
adam commented 2025-12-29 21:31:02 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 8, 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 (May 8, 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:31:02 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 7, 2025):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 7, 2025): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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#10404
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?