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

Unable to View IPAM > Prefixes when sorting by SCOPE #10656

New Issue
Closed
opened 2025-12-29 21:34:13 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:34:13 +01:00
Owner
Copy Link

Originally created by @Flol0 on GitHub (Jan 16, 2025).

Originally assigned to: @bctiemann on GitHub.

Deployment Type

Self-hosted

Triage priority

N/A

NetBox Version

v4.2.1

Python Version

3.11

Steps to Reproduce

  1. Click on IPAM followed by Prefixes
  2. In the Top Row click on SCOPE (which should sort the List by Scope Names)
  3. Reload the page because nothing is happening

Expected Behavior

The list should be sorted by SCOPE afterwards

Observed Behavior

Instead i got this message:
image

Workaround:

  1. In the top right go to your username -> Preferences
  2. Clear the Table configuration for table "PrefixTable"
Originally created by @Flol0 on GitHub (Jan 16, 2025). Originally assigned to: @bctiemann on GitHub. ### Deployment Type Self-hosted ### Triage priority N/A ### NetBox Version v4.2.1 ### Python Version 3.11 ### Steps to Reproduce 1. Click on IPAM followed by Prefixes 2. In the Top Row click on SCOPE (which should sort the List by Scope Names) 3. Reload the page because nothing is happening ### Expected Behavior The list should be sorted by SCOPE afterwards ### Observed Behavior Instead i got this message: ![image](https://github.com/user-attachments/assets/0af64e28-883c-4893-aad2-652626787f11) **Workaround:** 1. In the top right go to your username -> Preferences 2. Clear the Table configuration for table "PrefixTable"
adam added the type: bugstatus: acceptedseverity: medium labels 2025-12-29 21:34:13 +01:00
adam closed this issue 2025-12-29 21:34:13 +01:00
adam commented 2025-12-29 21:34:15 +01:00
Author
Owner
Copy Link

@bctiemann commented on GitHub (Jan 16, 2025):

It looks like our existing pattern

a75fa53d4d/netbox/ipam/tables/vlans.py (L39-L43)

is to set orderable=False on the scope field in these tables.

It would be more ideal to make the Scope column orderable, but given that we have this precedent I think at least consistency (and prevention of a crash) is an improvement.

@bctiemann commented on GitHub (Jan 16, 2025): It looks like our existing pattern https://github.com/netbox-community/netbox/blob/a75fa53d4d2c84cb4c129571a6da83b0f304ec20/netbox/ipam/tables/vlans.py#L39-L43 is to set `orderable=False` on the `scope` field in these tables. It would be more ideal to make the Scope column orderable, but given that we have this precedent I think at least consistency (and prevention of a crash) is an improvement.
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 severity: medium 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#10656
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?