Several list tables expose broken sortable columns #18

New Issue

MrUnknownDE · 2026-04-05T16:21:13+02:00

MrUnknownDE commented

2026-04-05 16:21:13 +02:00

Originally created by @pheus on 4/2/2026

NetBox Edition

NetBox Community

NetBox Version

v4.5.6

Python Version

3.12

Steps to Reproduce

Use a current stable NetBox release and create at least one object for each affected list view, with a value present in the column being sorted.
Open the affected list views and try to sort by the listed columns in ascending and descending order. Add the column through the table configuration first if it is not shown by default.
- Virtual circuit terminations: Account, Interface
- Config revisions: Is Active
- Virtual device contexts: Device
- Module types: Attributes
- Notifications: Icon
- Webhooks: SSL Validation
- VLAN translation rules: Name
- Tunnels: Terminations

Expected Behavior

Any column exposed as sortable should sort cleanly in both directions. Columns backed by computed or template-only values should be marked non-orderable, and table definitions should only reference valid column names and accessors.

Observed Behavior

Several tables currently expose broken sorting metadata. This appears to be a mix of invalid accessors or order_by targets, columns that should not be orderable, and mismatched column names in the table definitions. As a result, sorting the affected columns can raise an exception during queryset ordering or table rendering, or break when the affected column is enabled on the table.

*Originally created by @pheus on 4/2/2026* ### NetBox Edition NetBox Community ### NetBox Version v4.5.6 ### Python Version 3.12 ### Steps to Reproduce 1. Use a current stable NetBox release and create at least one object for each affected list view, with a value present in the column being sorted. 2. Open the affected list views and try to sort by the listed columns in ascending and descending order. Add the column through the table configuration first if it is not shown by default. - Virtual circuit terminations: **Account**, **Interface** - Config revisions: **Is Active** - Virtual device contexts: **Device** - Module types: **Attributes** - Notifications: **Icon** - Webhooks: **SSL Validation** - VLAN translation rules: **Name** - Tunnels: **Terminations** ### Expected Behavior Any column exposed as sortable should sort cleanly in both directions. Columns backed by computed or template-only values should be marked non-orderable, and table definitions should only reference valid column names and accessors. ### Observed Behavior Several tables currently expose broken sorting metadata. This appears to be a mix of invalid accessors or `order_by` targets, columns that should not be orderable, and mismatched column names in the table definitions. As a result, sorting the affected columns can raise an exception during queryset ordering or table rendering, or break when the affected column is enabled on the table.

MrUnknownDE closed this issue

2026-04-05 16:21:13 +02:00

MrUnknownDE added the status: accepted status: accepted type: bug type: bug severity: low type: bug netbox type: bug netbox netbox netbox netbox netbox netbox severity: low severity: low labels 2026-04-05 16:21:13 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label netbox netbox netbox netbox netbox netbox netbox severity: low severity: low severity: low status: accepted status: accepted type: bug type: bug type: bug type: bug

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#18