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

Display rack name next to site name in a circuit page #1509

New Issue
Closed
opened 2025-12-29 16:32:33 +01:00 by adam · 5 comments
adam commented 2025-12-29 16:32:33 +01:00
Owner
Copy Link

Originally created by @VictorRaim on GitHub (Jan 25, 2018).

[X] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 2.7.12
  • NetBox version: 2.2.8

Description

In webGUI when you display circuit and its A and Z termination sides. Only the site, termination device and port is displayed. Could it be better to also add the rack name next to the site termination ?

Something like this :
netbox rack circuit request feature

With this it would be easier to find informations when you have multiple racks in one site.

Originally created by @VictorRaim on GitHub (Jan 25, 2018). [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Environment * Python version: 2.7.12 * NetBox version: 2.2.8 ### Description In webGUI when you display circuit and its A and Z termination sides. Only the site, termination device and port is displayed. Could it be better to also add the rack name next to the site termination ? Something like this : ![netbox rack circuit request feature](https://user-images.githubusercontent.com/5525167/35383367-658f2204-01c2-11e8-80b2-ee301385b443.PNG) With this it would be easier to find informations when you have multiple racks in one site.
adam closed this issue 2025-12-29 16:32:33 +01:00
adam commented 2025-12-29 16:32:33 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 31, 2018):

The rack is inferred from the device on which the circuit is terminated. It doesn't seem likely that a lot of people will need this information included next to the device name.

@jeremystretch commented on GitHub (Jan 31, 2018): The rack is inferred from the device on which the circuit is terminated. It doesn't seem likely that a lot of people will need this information included next to the device name.
adam commented 2025-12-29 16:32:33 +01:00
Author
Owner
Copy Link

@manolab commented on GitHub (Feb 16, 2018):

I'd actually like that 👍

@manolab commented on GitHub (Feb 16, 2018): I'd actually like that 👍
adam commented 2025-12-29 16:32:33 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Feb 16, 2018):

Me too! It would help to minimize the end users action (prevent another search and associated possible human erors) when troubleshooting a circuit.

Could this be implemented using an on/off flag to be flexible ?

@AnythingOverIP commented on GitHub (Feb 16, 2018): Me too! It would help to minimize the end users action (prevent another search and associated possible human erors) when troubleshooting a circuit. Could this be implemented using an on/off flag to be flexible ?
adam commented 2025-12-29 16:32:33 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Feb 22, 2018):

I really have to agree with @jeremystretch here. Does not seem like a bunch of ROI, and it starts a potential ui noise creep.

Click the device to see what rack it’s in, or generate a report if you need that view. Maybe this gets added later as netbox addresses more major features.

Maybe if someone else besides Jeremy wants to implement this, they can do a PR, but this badly sounds like a nice to have.

@ryanmerolle commented on GitHub (Feb 22, 2018): I really have to agree with @jeremystretch here. Does not seem like a bunch of ROI, and it starts a potential ui noise creep. Click the device to see what rack it’s in, or generate a report if you need that view. Maybe this gets added later as netbox addresses more major features. Maybe if someone else besides Jeremy wants to implement this, they can do a PR, but this badly sounds like a nice to have.
adam commented 2025-12-29 16:32:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 23, 2018):

Yeah, I've got to reject this one as there's no direct relationship between a circuit and the rack in which the devices it's terminated to is installed. That information as well as any other information concerning the device is provided on the device view.

@jeremystretch commented on GitHub (Feb 23, 2018): Yeah, I've got to reject this one as there's no direct relationship between a circuit and the rack in which the devices it's terminated to is installed. That information as well as any other information concerning the device is provided on the device view.
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#1509
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?