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

Location of the rack in the device menu #5984

New Issue
Closed
opened 2025-12-29 19:35:10 +01:00 by adam · 8 comments
adam commented 2025-12-29 19:35:10 +01:00
Owner
Copy Link

Originally created by @KosenkoIvan on GitHub (Jan 21, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

nexbox (v3.1.5)

Feature type

Change to existing functionality

Proposed functionality

It would be convenient if the racks were displayed not only in the racks menu but also in the devices menu. This would simplify switching between devices. That is, we will not need to go to the racks menu and select the object we need again, but instantly select the desired device.
Screenshot_4
Screenshot_3

Use case

This would simplify switching between devices. That is, we will not need to go to the racks menu and select the object we need again, but instantly select the desired device.

Database changes

No response

External dependencies

No response

Originally created by @KosenkoIvan on GitHub (Jan 21, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version nexbox (v3.1.5) ### Feature type Change to existing functionality ### Proposed functionality It would be convenient if the racks were displayed not only in the racks menu but also in the devices menu. This would simplify switching between devices. That is, we will not need to go to the racks menu and select the object we need again, but instantly select the desired device. ![Screenshot_4](https://user-images.githubusercontent.com/97949308/150517231-104b59d1-10bb-4ed3-bee3-654af3145efe.png) ![Screenshot_3](https://user-images.githubusercontent.com/97949308/150517234-d84009f8-2169-46ce-8b0c-8cd2f961bd21.png) ### Use case This would simplify switching between devices. That is, we will not need to go to the racks menu and select the object we need again, but instantly select the desired device. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:35:10 +01:00
adam closed this issue 2025-12-29 19:35:10 +01:00
adam commented 2025-12-29 19:35:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2022):

Probably related to #4434

@jeremystretch commented on GitHub (Jan 26, 2022): Probably related to #4434
adam commented 2025-12-29 19:35:20 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 28, 2022):

I don't think devices should be showing the rack they are in, at least in my opinion. Conflating two different views, is something I think we should avoid, as it will add to the maintenance burden.

@DanSheps commented on GitHub (Jan 28, 2022): I don't think devices should be showing the rack they are in, at least in my opinion. Conflating two different views, is something I think we should avoid, as it will add to the maintenance burden.
adam commented 2025-12-29 19:35:20 +01:00
Author
Owner
Copy Link

@KosenkoIvan commented on GitHub (Feb 3, 2022):

Before NetBox, we used RackTables and racks were shown there. From my own experience I can say about the convenience.

@KosenkoIvan commented on GitHub (Feb 3, 2022): Before NetBox, we used RackTables and racks were shown there. From my own experience I can say about the convenience.
adam commented 2025-12-29 19:35:20 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Mar 1, 2022):

How about adding the elevations button to the "Rack" row on the left hand "Device" pane which redirects to the elevations view pre-filtered to just one rack?

@cpmills1975 commented on GitHub (Mar 1, 2022): How about adding the elevations button to the "Rack" row on the left hand "Device" pane which redirects to the elevations view pre-filtered to just one rack?
adam commented 2025-12-29 19:35:21 +01:00
Author
Owner
Copy Link

@KosenkoIvan commented on GitHub (Mar 1, 2022):

I do not think that such an implementation will be correct, because the advantage of a solid display of the rack is that it would be possible not only to view the appearance of the rack, but also to switch the next device in 1 click.

@KosenkoIvan commented on GitHub (Mar 1, 2022): I do not think that such an implementation will be correct, because the advantage of a solid display of the rack is that it would be possible not only to view the appearance of the rack, but also to switch the next device in 1 click.
adam commented 2025-12-29 19:35:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 6, 2022):

I think it makes sense to embed the rack elevation, however in doing so we'd certainly want to highlight the device itself within the SVG drawing. I'm going to mark this as blocked by #4434, which seeks to do just that.

@jeremystretch commented on GitHub (Apr 6, 2022): I think it makes sense to embed the rack elevation, however in doing so we'd certainly want to highlight the device itself within the SVG drawing. I'm going to mark this as blocked by #4434, which seeks to do just that.
adam commented 2025-12-29 19:35:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

If pursued, this work needs to be done on a v3.3 or later release (to enable device highlighting).

@jeremystretch commented on GitHub (Jul 27, 2022): If pursued, this work needs to be done on a v3.3 or later release (to enable device highlighting).
adam commented 2025-12-29 19:35:22 +01:00
Author
Owner
Copy Link

@SimonSchmitz commented on GitHub (Oct 13, 2022):

Is there a way to display the racks on the left? Because now all plug-in extensions are displayed under the rack.

Bildschirmfoto 2022-10-13 um 18 36 30

@SimonSchmitz commented on GitHub (Oct 13, 2022): Is there a way to display the racks on the left? Because now all plug-in extensions are displayed under the rack. ![Bildschirmfoto 2022-10-13 um 18 36 30](https://user-images.githubusercontent.com/29935460/195654990-1b65469b-75cf-4fd3-be2a-c05c23a74734.png)
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 status: accepted 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#5984
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?