Extend the filter feature for Dashboard Widgets #7923

Closed
opened 2025-12-29 20:30:00 +01:00 by adam · 2 comments
Owner

Originally created by @peteeckel on GitHub (Apr 18, 2023).

NetBox version

v3.5-beta2

Feature type

Change to existing functionality

Proposed functionality

#12136 introduced the option to apply filters to Dashboard Widgets, which is great.

There is, however, a restriction that limits the use of the feature, as a filter can only be applied to all models listed in, for instance, an Object Count widget, and each model can only be listed once. It would be much more useful if a model could be added multiple times, with different filters per occurrence.

Use case

A possible use case is to list devices and racks per tenant, location or site, or IP addresses per VRF in one widget, but I'm sure there are many more.

Database changes

No response

External dependencies

No response

Originally created by @peteeckel on GitHub (Apr 18, 2023). ### NetBox version v3.5-beta2 ### Feature type Change to existing functionality ### Proposed functionality #12136 introduced the option to apply filters to Dashboard Widgets, which is great. There is, however, a restriction that limits the use of the feature, as a filter can only be applied to all models listed in, for instance, an Object Count widget, and each model can only be listed once. It would be much more useful if a model could be added multiple times, with different filters per occurrence. ### Use case A possible use case is to list devices and racks per tenant, location or site, or IP addresses per VRF in one widget, but I'm sure there are many more. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 20:30:00 +01:00
adam closed this issue 2025-12-29 20:30:01 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 4, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 4, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Sep 4, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 4, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7923