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

Next/Previous device buttons in Device view #3253

New Issue
Closed
opened 2025-12-29 18:27:08 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:27:08 +01:00
Owner
Copy Link

Originally created by @rkerr on GitHub (Jan 31, 2020).

Proposed Functionality

In the Rack view there are Next Rack and Previous Rack buttons to cycle through racks in a site. These are quite useful, however similar functionality is missing from other screens. I would suggest adding this to the Device view in order to allow you to cycle through other devices in the same rack.

Use Case

When making a change I often find it is a change that affects a number of devices that are physically next to each other in the same rack. It would save some clicks to be able to go direct to the next device in the rack having completed an edit.

Originally created by @rkerr on GitHub (Jan 31, 2020). ### Proposed Functionality In the Rack view there are Next Rack and Previous Rack buttons to cycle through racks in a site. These are quite useful, however similar functionality is missing from other screens. I would suggest adding this to the Device view in order to allow you to cycle through other devices in the same rack. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case When making a change I often find it is a change that affects a number of devices that are physically next to each other in the same rack. It would save some clicks to be able to go direct to the next device in the rack having completed an edit.
adam closed this issue 2025-12-29 18:27:08 +01:00
adam commented 2025-12-29 18:27:09 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Feb 3, 2020):

This issue has been closed as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).

@kobayashi commented on GitHub (Feb 3, 2020): This issue has been closed as it does not conform to one of the [provided templates](https://github.com/digitalocean/netbox/issues/new/choose) as required by the [contributing guide](https://github.com/digitalocean/netbox/blob/master/CONTRIBUTING.md). If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely).
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
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#3253
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?