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 custom ordering of racks in the elevations list view #1440

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

Originally created by @chrispcall on GitHub (Dec 6, 2017).

Originally assigned to: @jeremystretch on GitHub.

Just installed the software and i'm loving it with one visual exception: It would be nice to have an option to display the rack elevation view mirrored when we are looking at the back view. I spend most of my time behind my racks and in the current view, I can only look at the the way they are positioned (L-R) in the front view and switching to back view shows me the back of each rack but they are out of order for how I am used to looking at them in real life.

Hope that makes sense.

Basically I would like an option for rack elevation views to look like this:
Front view:
[A-1] [A-2] [A-3] [A-4]

Then back view:
[A-4] [A-3] [A-2] [A-1]

I searched open and closed requests and did not see anything like this. Also, this is my first github anything, so please go easy on my ignorance!

Issue type

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

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.6

Description

Originally created by @chrispcall on GitHub (Dec 6, 2017). Originally assigned to: @jeremystretch on GitHub. Just installed the software and i'm loving it with one visual exception: It would be nice to have an option to display the rack elevation view mirrored when we are looking at the back view. I spend most of my time behind my racks and in the current view, I can only look at the the way they are positioned (L-R) in the front view and switching to back view shows me the back of each rack but they are out of order for how I am used to looking at them in real life. Hope that makes sense. Basically I would like an option for rack elevation views to look like this: Front view: [A-1] [A-2] [A-3] [A-4] Then back view: [A-4] [A-3] [A-2] [A-1] I searched open and closed requests and did not see anything like this. Also, this is my first github anything, so please go easy on my ignorance! <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. For assistance with installation issues, or for any other issues other than those listed below, please raise your topic for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. Due to an excessive backlog of feature requests, we are not currently accepting any proposals which extend NetBox's feature scope. Do not prepend any sort of tag to your issue's title. An administrator will review your issue and assign labels as appropriate. ---> ### Issue type [X ] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) If you are submitting a bug report and have made any changes to the code base, please first validate that your bug can be recreated while running an official release. --> ### Environment * Python version: 3.5.2 * NetBox version: 2.2.6 <!-- BUG REPORTS must include: * A list of the steps needed for someone else to reproduce the bug * A description of the expected and observed behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description
adam added the status: acceptedtype: feature labels 2025-12-29 16:32:12 +01:00
adam closed this issue 2025-12-29 16:32:12 +01:00
adam commented 2025-12-29 16:32:12 +01:00
Author
Owner
Copy Link

@chrispcall commented on GitHub (Dec 7, 2017):

@jasonguy Are you talking about something different than elevation view? That shows you the racks in a row. I'm just looking for a small feature WITHIN that view.

@chrispcall commented on GitHub (Dec 7, 2017): @jasonguy Are you talking about something different than elevation view? That shows you the racks in a row. I'm just looking for a small feature WITHIN that view.
adam commented 2025-12-29 16:32:12 +01:00
Author
Owner
Copy Link

@jasonguy commented on GitHub (Dec 7, 2017):

@chrispcall My mistake. I had not created multiple racks yet. I agree that the "rear" view should be reversed, as if you "walked around the back", everything would be reversed left to right. Good idea...I deleted my useless comment. :)

@jasonguy commented on GitHub (Dec 7, 2017): @chrispcall My mistake. I had not created multiple racks yet. I agree that the "rear" view should be reversed, as if you "walked around the back", everything would be reversed left to right. Good idea...I deleted my useless comment. :)
adam commented 2025-12-29 16:32:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2017):

Rather than simply flipping the ordering, we probably want to expose a way for the user to choose how the racks are sorted. (This is accomplished in most list views using django-tables' built-in RequestConfig(), which allows sorting by column header.)

@jeremystretch commented on GitHub (Dec 13, 2017): Rather than simply flipping the ordering, we probably want to expose a way for the user to choose how the racks are sorted. (This is accomplished in most list views using django-tables' built-in `RequestConfig()`, which allows sorting by column header.)
adam commented 2025-12-29 16:32:13 +01:00
Author
Owner
Copy Link

@DerDanilo commented on GitHub (Jun 26, 2019):

Since this feature request was accepted we're wondering when it's going to be implemented.
Any news on this? This doesn't sound to difficult to do but I may be wrong.

@DerDanilo commented on GitHub (Jun 26, 2019): Since this feature request was accepted we're wondering when it's going to be implemented. Any news on this? This doesn't sound to difficult to do but I may be wrong.
adam commented 2025-12-29 16:32:13 +01:00
Author
Owner
Copy Link

@jasonthrasher commented on GitHub (Mar 12, 2020):

We'd like for this feature to accomplish 2 things.

  1. Allow you to specify the sort order per rack group. For example, if we number racks based on their relative position to a defined wall then opposing rows would have 1-4 going left to right and opposite row would have 1-4 going right to left

back front back
[1] [1]
[2] [2]
[3] [3]
[4] [4]

  1. Reverse specified sort order when selecting "rear" option. This would allow you to retain the physical layout of the rack and you look at it from the back.
@jasonthrasher commented on GitHub (Mar 12, 2020): We'd like for this feature to accomplish 2 things. 1. Allow you to specify the sort order per rack group. For example, if we number racks based on their relative position to a defined wall then opposing rows would have 1-4 going left to right and opposite row would have 1-4 going right to left back front back [1] [1] [2] [2] [3] [3] [4] [4] 2. Reverse specified sort order when selecting "rear" option. This would allow you to retain the physical layout of the rack and you look at it from the back.
adam commented 2025-12-29 16:32:13 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 7, 2020):

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. Please see our contributing guide.

@stale[bot] commented on GitHub (Sep 7, 2020): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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#1440
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?