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

Allow arbitrary rack selection in Rack Elevation view #2615

New Issue
Closed
opened 2025-12-29 18:20:25 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:20:25 +01:00
Owner
Copy Link

Originally created by @BlessJah on GitHub (May 15, 2019).

Environment

  • NetBox version: 2.5.11

Proposed Functionality

Allow selection of arbitrary racks in Rack Elevations view.

Use Case

It is not always possible to limit racks shown in Rack Elevations using existing filters. Physical DC layout might be misaligned with groups/tenants/roles, or racks are shared.

Following feature and MR would allow operator to select arbitrary racks for Rack Elevation and other view where RackFilterForm is used.

Database Changes

None.

External Dependencies

None.

Originally created by @BlessJah on GitHub (May 15, 2019). ### Environment * NetBox version: 2.5.11 ### Proposed Functionality Allow selection of arbitrary racks in Rack Elevations view. ### Use Case It is not always possible to limit racks shown in Rack Elevations using existing filters. Physical DC layout might be misaligned with groups/tenants/roles, or racks are shared. Following feature and MR would allow operator to select arbitrary racks for Rack Elevation and other view where `RackFilterForm` is used. ### Database Changes None. ### External Dependencies None.
adam added the status: accepted label 2025-12-29 18:20:25 +01:00
adam closed this issue 2025-12-29 18:20:26 +01:00
adam commented 2025-12-29 18:20:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 29, 2019):

What is the specific implementation being proposed?

@jeremystretch commented on GitHub (May 29, 2019): What is the specific implementation being proposed?
adam commented 2025-12-29 18:20:26 +01:00
Author
Owner
Copy Link

@BlessJah commented on GitHub (May 29, 2019):

I propose adding multiple choice field to rack search form.

Current set of fields does not include multiple choice of racks. Search field provides "fuzzy" search as opposed to arbitrary selection, thus new field is complementary to existing fields.

select_rack

@BlessJah commented on GitHub (May 29, 2019): I propose adding multiple choice field to rack search form. Current set of fields does not include multiple choice of racks. Search field provides "fuzzy" search as opposed to arbitrary selection, thus new field is complementary to existing fields. ![select_rack](https://user-images.githubusercontent.com/835808/58588840-e01d5200-8260-11e9-991d-7f49beb8c7d1.png)
adam commented 2025-12-29 18:20:27 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Jun 11, 2019):

If racks can be displayed in the order they are added, that would be useful. Looking towards the front of some of my racks, they are numbered 100, 99, 98 in that order - the front faces in to the cold aisle and the numbering goes up the hall so racks on the left of the cold aisle are numbered 98, 99, 100, but on the right the order appears right to left.

@cpmills1975 commented on GitHub (Jun 11, 2019): If racks can be displayed in the order they are added, that would be useful. Looking towards the front of some of my racks, they are numbered 100, 99, 98 in that order - the front faces in to the cold aisle and the numbering goes up the hall so racks on the left of the cold aisle are numbered 98, 99, 100, but on the right the order appears right to left.
adam commented 2025-12-29 18:20:27 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 25, 2019):

Related to #1755

@jeremystretch commented on GitHub (Jun 25, 2019): Related to #1755
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
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#2615
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?