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

Enable sorting REST API results #6268

New Issue
Closed
opened 2025-12-29 19:38:46 +01:00 by adam · 0 comments
adam commented 2025-12-29 19:38:46 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Mar 29, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.1.10

Feature type

New functionality

Proposed functionality

Allow users to specify a field by which the results of a REST API query should be ordered. For example:

GET /api/dcim/sites/?ordering=tenant

This seems easily feasible by adding DRF's built-in OrderingFilter to DEFAULT_FILTER_BACKENDS. We'll also need to define ordering_fields on each API view set.

Edit: This was first proposed in #3650.

Use case

Allows for more efficiently retrieving a set of objects in a particular order via the REST API.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Mar 29, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.1.10 ### Feature type New functionality ### Proposed functionality Allow users to specify a field by which the results of a REST API query should be ordered. For example: ``` GET /api/dcim/sites/?ordering=tenant ``` This seems easily feasible by adding DRF's built-in [OrderingFilter](https://www.django-rest-framework.org/api-guide/filtering/#orderingfilter) to `DEFAULT_FILTER_BACKENDS`. We'll also need to define `ordering_fields` on each API view set. Edit: This was first proposed in #3650. ### Use case Allows for more efficiently retrieving a set of objects in a particular order via the REST API. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:38:46 +01:00
adam closed this issue 2025-12-29 19:38:47 +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: feature
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#6268
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?