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 Rack" in rack view not scoped to rack group #2985

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

Originally created by @bellwood on GitHub (Oct 29, 2019).

Environment

  • Python version: 3.6.9
  • NetBox version: 2.6.6

Steps to Reproduce

  1. View all racks
  2. Filter by site
  3. Filter by rack group
  4. View the first rack returned
  5. Click "Next Rack"

Expected Behavior

Should display the next rack in the rack group at that site

Observed Behavior

Gives the next rack at the site, as a whole, sorted by name

Edit:
The current behavior is less than ideal. As we go through sites to verify documentation we go rack-by-rack within a rack group. The way "next rack" currently works, we'd have to physically go to other rack groups or do a lot of clicking through "next rack" until the next rack in the current group comes up.

Perhaps when rack_group is part of the filter clicking on those racks can add the group to the query string and/or the pagination for "next rack" - if the route(s) support this behavior.

Originally created by @bellwood on GitHub (Oct 29, 2019). ### Environment * Python version: 3.6.9 * NetBox version: 2.6.6 ### Steps to Reproduce 1. View all racks 2. Filter by site 3. Filter by rack group 4. View the first rack returned 5. Click "Next Rack" <!-- What did you expect to happen? --> ### Expected Behavior Should display the next rack in the rack group at that site <!-- What happened instead? --> ### Observed Behavior Gives the next rack at the site, as a whole, sorted by name Edit: The current behavior is less than ideal. As we go through sites to verify documentation we go rack-by-rack within a rack group. The way "next rack" currently works, we'd have to physically go to other rack groups or do a lot of clicking through "next rack" until the next rack in the current group comes up. Perhaps when rack_group is part of the filter clicking on those racks can add the group to the query string and/or the pagination for "next rack" - if the route(s) support this behavior.
adam added the type: bugstatus: accepted labels 2025-12-29 18:24:25 +01:00
adam closed this issue 2025-12-29 18:24:25 +01:00
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: bug
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#2985
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?