Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show rack-list dropdown in rack view #10987

Closed
PieterL75 opened this issue Nov 20, 2022 · 4 comments · Fixed by #11779
Closed

Show rack-list dropdown in rack view #10987

PieterL75 opened this issue Nov 20, 2022 · 4 comments · Fixed by #11779
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application

Comments

@PieterL75
Copy link
Contributor

NetBox version

v3.3.8

Feature type

Change to existing functionality

Proposed functionality

When viewing a rack, you have the 'previous' and 'next' button.
image

Add a 'dropdown' between those 2 buttons, so that all racks of a location (or site if no location is set) are selectable
image

Use case

This will provide a faster navigation between the racks.
Another option, is to display all racks in a full-width bar with horizontal scrolling
image

Database changes

No response

External dependencies

No response

@PieterL75 PieterL75 added the type: feature Introduction of new functionality to the application label Nov 20, 2022
@ITJamie
Copy link
Contributor

ITJamie commented Nov 22, 2022

I also like this idea. Racktables had a left and right button when viewing a rack to quickly move between racks in a row. It was useful if for getting to the rack ether side of current rack in a single click

@jeremystretch jeremystretch added the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label Dec 9, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Feb 8, 2023

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Feb 8, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation pending closure Requires immediate attention to avoid being closed for inactivity labels Feb 17, 2023
@PieterL75
Copy link
Contributor Author

@jeremystretch I found the BS classes to auto hide/show the 2 different navs, depending on the size of the screen.
I like it :-)

@PieterL75
Copy link
Contributor Author

The bar might get pretty wide when there are a lot of racks in one site.. Maybe a 'pagination' style would be a better approach, showing only 3 racks before and 3 racks behind the current rack, with arrows
< R201 R203 R204 [R205] R206 R207 R208 >

jeremystretch added a commit that referenced this issue Apr 24, 2023
* Intial. 2 ways the racknavigation displayed

* show active rack in dropdown

* auto hide/show when viewport reduces

* Dropdown only

* Update links to use get_absolute_url()

---------

Co-authored-by: Pieter Lambrecht <[email protected]>
Co-authored-by: jeremystretch <[email protected]>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants