starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Clearing the ordering of a table does not clear the ordering key from the UserConfig data #8201

New Issue
Closed
opened 2025-12-29 20:33:44 +01:00 by adam · 0 comments
adam commented 2025-12-29 20:33:44 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Jun 15, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.5.3

Python version

3.8

Steps to Reproduce

  1. Open the sites list and order the entries by name.
  2. In a shell, retrieve the UserConfig instance for your user and inspect the entry for tables.SiteTable.ordering:
>>> uc=UserConfig.objects.get(user__username='admin')
>>> uc.data['tables']['SiteTable']['ordering']
['name']
  1. In the UI, clear the applied ordering by clicking the X in the column header.
  2. Refresh and re-inspect the UserConfig data:
>>> uc.refresh_from_db()
>>> uc.data['tables']['SiteTable']['ordering']
['']

Expected Behavior

The ordering key should be removed from the data, as there is no longer any preference stored.

Observed Behavior

ordering is set to a list containing an empty string. This does not effect any breaking behavior AFAICT, however it should be cleaned up as it can pose complications.

Originally created by @jeremystretch on GitHub (Jun 15, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.5.3 ### Python version 3.8 ### Steps to Reproduce 1. Open the sites list and order the entries by name. 2. In a shell, retrieve the UserConfig instance for your user and inspect the entry for `tables.SiteTable.ordering`: ``` >>> uc=UserConfig.objects.get(user__username='admin') >>> uc.data['tables']['SiteTable']['ordering'] ['name'] ``` 3. In the UI, clear the applied ordering by clicking the X in the column header. 4. Refresh and re-inspect the UserConfig data: ``` >>> uc.refresh_from_db() >>> uc.data['tables']['SiteTable']['ordering'] [''] ``` ### Expected Behavior The `ordering` key should be removed from the data, as there is no longer any preference stored. ### Observed Behavior `ordering` is set to a list containing an empty string. This does not effect any breaking behavior AFAICT, however it should be cleaned up as it can pose complications.
adam added the type: bugstatus: accepted labels 2025-12-29 20:33:44 +01:00
adam closed this issue 2025-12-29 20:33:45 +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#8201
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?