Object Count Widget filters ignore lists #8236

New Issue

adam · 2025-12-29T20:34:10+01:00

adam commented

2025-12-29 20:34:10 +01:00

Originally created by @dreng on GitHub (Jun 23, 2023).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.5.4

Python version

3.9

Steps to Reproduce

Create a new widget

Widget type "Object Counts"
Models: DCIM > Device
Object filters: { "manufacturer_id": ["1", "2"] }
(replace "1" and "2" with valid IDs in your environment)

Check number of counted objects

Expected Behavior

I'd expect NetBox to take lists into account like shown above and just like the corresponding URL does: https://netbox.tld/dcim/devices/?manufacturer_id=1&manufacturer_id=2

As per https://github.com/netbox-community/netbox/issues/12742, Object Count filters employ standard UI filters rather than low-level queryset filters since v3.5.3. While this is a good design decision, queryset filters gave the ability to use logical OR filters. Since Object List filters take lists into account, I'd expect Object Count filters to do the same.

Observed Behavior

The number of counted objects is always equal to the number of all devices. Nothing will be filtered. The filter works if you use a single string and not a list, e.g. { "manufacturer_id": "1" }

This behaviour is not the case with Object Lists.

Originally created by @dreng on GitHub (Jun 23, 2023). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.5.4 ### Python version 3.9 ### Steps to Reproduce 1. Create a new widget - Widget type "Object Counts" - Models: DCIM > Device - Object filters: { "manufacturer_id": ["1", "2"] } (replace "1" and "2" with valid IDs in your environment) 2. Check number of counted objects ### Expected Behavior I'd expect NetBox to take lists into account like shown above and just like the corresponding URL does: https://netbox.tld/dcim/devices/?manufacturer_id=1&manufacturer_id=2 As per https://github.com/netbox-community/netbox/issues/12742, Object Count filters employ standard UI filters rather than low-level queryset filters since v3.5.3. While this is a good design decision, queryset filters gave the ability to use logical OR filters. Since Object List filters take lists into account, I'd expect Object Count filters to do the same. ### Observed Behavior The number of counted objects is always equal to the number of all devices. Nothing will be filtered. The filter works if you use a single string and not a list, e.g. { "manufacturer_id": "1" } This behaviour is not the case with Object Lists.

adam added the type: bug status: accepted severity: low labels 2025-12-29 20:34:10 +01:00

adam closed this issue

2025-12-29 20:34:10 +01:00

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#8236