Allow reports to be sorted by object information or status. #2195

New Issue

adam · 2025-12-29T17:23:23+01:00

adam commented

2025-12-29 17:23:23 +01:00

Originally created by @chaomodus on GitHub (Dec 11, 2018).

Description

Allow from the reports UI, or from the reports API, the consumer to specify sort column(s) and sort order, such as by object creation date, or by status (error, warning, success).

Use Case

Our use case is that we use reports to for example determine if hardware is old and should be considered for replacement. It would be preferable to be able to get this report with log_success sorted to the bottom to focus attention on the log_error lines which indicate old hardware. This feature is generic however and would likely have numerous uses.

Originally created by @chaomodus on GitHub (Dec 11, 2018). ### Description Allow from the reports UI, or from the reports API, the consumer to specify sort column(s) and sort order, such as by object creation date, or by status (error, warning, success). ### Use Case Our use case is that we use reports to for example determine if hardware is old and should be considered for replacement. It would be preferable to be able to get this report with log_success sorted to the bottom to focus attention on the log_error lines which indicate old hardware. This feature is generic however and would likely have numerous uses.

adam closed this issue

2025-12-29 17:23:23 +01:00

adam commented

2025-12-29 17:23:24 +01:00

@paravoid commented on GitHub (Dec 14, 2018):

It would be neat perhaps to have an option to hide successes entirely (perhaps even the default?). Otherwise one would have go go over a few thousand successes only (or sort them) just to identify a handful of failures.

@paravoid commented on GitHub (Dec 14, 2018): It would be neat perhaps to have an option to hide successes entirely (perhaps even the default?). Otherwise one would have go go over a few thousand successes only (or sort them) just to identify a handful of failures.

adam commented

2025-12-29 17:23:24 +01:00

@jeremystretch commented on GitHub (Dec 19, 2018):

Individual successes and failures logged within a report are not orderable at the database level: These are all stored as a single JSON object and listed in the order they were generated. You can achieve a particular ordering of results by calling log_success(), log_failure(), etc. in the desired order within the report. For example:

infos = []
for device in Device.objects.all():
    if not device.serial:
        self.log_failure(device, "Mising serial number!")
    else:
        infos.append(device)
for info in infos:
    self.log_info(device, "{} has a serial number: {}".format(device.name, device.serial))

@jeremystretch commented on GitHub (Dec 19, 2018): Individual successes and failures logged within a report are not orderable at the database level: These are all stored as a single JSON object and listed in the order they were generated. You can achieve a particular ordering of results by calling `log_success()`, `log_failure()`, etc. in the desired order within the report. For example: ``` infos = [] for device in Device.objects.all(): if not device.serial: self.log_failure(device, "Mising serial number!") else: infos.append(device) for info in infos: self.log_info(device, "{} has a serial number: {}".format(device.name, device.serial)) ```

adam referenced this issue

2025-12-29 22:20:54 +01:00

[PR #2195] [CLOSED] add exact address match query to IPAddressFilter #12326

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#2195