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

Rack elevations layout #11209

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

Originally created by @doc-sheet on GitHub (May 21, 2025).

NetBox version

v4.3.1

Feature type

Change to existing functionality

Proposed functionality

Hello.
My suggestion is to remove white-space: nowrap from rack elevations block.

Use case

Right now it is kinda rough to visually look for rack with horizontal scroll. Would you mind to remove forced horizontal layout or make it optional?

Let's look into demo instance with default vertical scroll. I personally think it is better.

Image

:

Database changes

No response

External dependencies

No response

Originally created by @doc-sheet on GitHub (May 21, 2025). ### NetBox version v4.3.1 ### Feature type Change to existing functionality ### Proposed functionality Hello. My suggestion is to remove `white-space: nowrap` from [rack elevations block](https://github.com/netbox-community/netbox/blob/51d046b1f50b0cf8c56903ebefe43aa2caff13eb/netbox/templates/dcim/rack_elevation_list.html#L46). ### Use case Right now it is kinda rough to visually look for rack with horizontal scroll. Would you mind to remove forced horizontal layout or make it optional? Let's look into demo instance with default vertical scroll. I personally think it is better. ![Image](https://github.com/user-attachments/assets/8b10ad78-c4fa-42d6-8d15-a853f2692e41) : ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 21:41:58 +01:00
adam closed this issue 2025-12-29 21:41:58 +01:00
adam commented 2025-12-29 21:41:59 +01:00
Author
Owner
Copy Link

@cybarox commented on GitHub (May 22, 2025):

I also often find horizontal scrolling impractical, especially with larger sites. I would like to see an option to group the rack elevations by location, so you can still display the rack rows together. Optionally, there could also be a user setting such a max-racks-per-row value.

@cybarox commented on GitHub (May 22, 2025): I also often find horizontal scrolling impractical, especially with larger sites. I would like to see an option to group the rack elevations by location, so you can still display the rack rows together. Optionally, there could also be a user setting such a max-racks-per-row value.
adam commented 2025-12-29 21:41:59 +01:00
Author
Owner
Copy Link

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

This seems very unnatural IMO. Racks are presented horizontally both because that's typically how they appear in person and because racks can vary in height. The intended workflow is view one group or row of racks at a time.

@jeremystretch commented on GitHub (May 22, 2025): This seems very unnatural IMO. Racks are presented horizontally both because that's typically how they appear in person and because racks can vary in height. The intended workflow is view one group or row of racks at a time.
adam commented 2025-12-29 21:42:00 +01:00
Author
Owner
Copy Link

@domreuter-prog commented on GitHub (Oct 29, 2025):

I want to support the idea and add my two cent - before introducing netbox we used Excel sheets. There we had one cell per rack unit, 47 cells (plus header) grouped to one rack, the grouped racks arranged in rows and columns in the same way the racks are arranged in the data center. That would mean kind of a crossover between the eleviation function and the floor plan plugin.

@domreuter-prog commented on GitHub (Oct 29, 2025): I want to support the idea and add my two cent - before introducing netbox we used Excel sheets. There we had one cell per rack unit, 47 cells (plus header) grouped to one rack, the grouped racks arranged in rows and columns in the same way the racks are arranged in the data center. That would mean kind of a crossover between the eleviation function and the floor plan plugin.
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: under review 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#11209
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?