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

List items tagged with a specific tag #4033

New Issue
Closed
opened 2025-12-29 18:32:43 +01:00 by adam · 9 comments
adam commented 2025-12-29 18:32:43 +01:00
Owner
Copy Link

Originally created by @marinbernard-pep06 on GitHub (Aug 27, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.9.1

Proposed Functionality

Currently, Netbox allows to list the number of items tagged with each tag, but offers no simple way to list those items. I propose to add a view to display a list of all items tagged with a specific tag. The user would access this view by clicking on the tag name.

This feature request was first discussed on the mailing list.

Use Case

This change would allow a user to list arbitrary items flagged with a specific tag. Internally, we use tags to flag items needing attention. This would greatly improve the work or our support team.

Database Changes

None.

External Dependencies

None.

Originally created by @marinbernard-pep06 on GitHub (Aug 27, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.9.1 ### Proposed Functionality Currently, Netbox allows to list the number of items tagged with each tag, but offers no simple way to list those items. I propose to add a view to display a list of all items tagged with a specific tag. The user would access this view by clicking on the tag name. This feature request was first [discussed on the mailing list](https://groups.google.com/g/netbox-discuss/c/jtNTDfaPSrk). ### Use Case This change would allow a user to list arbitrary items flagged with a specific tag. Internally, we use tags to flag items needing attention. This would greatly improve the work or our support team. ### Database Changes None. ### External Dependencies None.
adam closed this issue 2025-12-29 18:32:43 +01:00
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 27, 2020):

This is because listing various types of objects together often doesn't make sense. Each model has its own set of attributes that help uniquely distinguish it to the user, and these are impossible to combine in a single table. For example, it would not make sense to list the same IP address multiple times without also displaying the VRF to which each is assigned, but that wouldn't make sense when also showing devices. It's also extremely inefficient to pull in arbitrary objects by following every tag assignment.

To find items with a particular tag assigned, you'll need to first navigate to the list view for that model, and then filter by the desired tag. (Also note that when viewing a particular object, clicking on an assigned tag will take you to a list of all objects of that type with the tag assigned.)

@jeremystretch commented on GitHub (Aug 27, 2020): This is because listing various types of objects together often doesn't make sense. Each model has its own set of attributes that help uniquely distinguish it to the user, and these are impossible to combine in a single table. For example, it would not make sense to list the same IP address multiple times without also displaying the VRF to which each is assigned, but that wouldn't make sense when also showing devices. It's also extremely inefficient to pull in arbitrary objects by following every tag assignment. To find items with a particular tag assigned, you'll need to first navigate to the list view for that model, and then filter by the desired tag. (Also note that when viewing a particular object, clicking on an assigned tag will take you to a list of all objects of that type with the tag assigned.)
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@marinbernard-pep06 commented on GitHub (Aug 27, 2020):

To find items with a particular tag assigned, you'll need to first navigate to the list view for that model, and then filter by the desired tag. (Also note that when viewing a particular object, clicking on an assigned tag will take you to a list of all objects of that type with the tag assigned.)

Yes, this is convenient enough as long as the model has a view, but it's not always true: for instance, we would really need a way to list all front ports/rear ports/interfaces flagged with a specific tag, regardless of the owning device, as it would allow us to easily tag identify failed/misconfigured ports and list them when needed. Today, we know how many of these ports have a specific tags, but we're unable to know which ones.

@marinbernard-pep06 commented on GitHub (Aug 27, 2020): > To find items with a particular tag assigned, you'll need to first navigate to the list view for that model, and then filter by the desired tag. (Also note that when viewing a particular object, clicking on an assigned tag will take you to a list of all objects of that type with the tag assigned.) Yes, this is convenient enough as long as the model has a view, but it's not always true: for instance, we would really need a way to list all front ports/rear ports/interfaces flagged with a specific tag, regardless of the owning device, as it would allow us to easily tag identify failed/misconfigured ports and list them when needed. Today, we know how many of these ports have a specific tags, but we're unable to know which ones.
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@marinbernard-pep06 commented on GitHub (Aug 27, 2020):

Well, I just discovered that front ports et al. had a view. Sorry for the noise. Thank you!

@marinbernard-pep06 commented on GitHub (Aug 27, 2020): Well, I just discovered that front ports et al. had a view. Sorry for the noise. Thank you!
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@Tavoons commented on GitHub (Aug 27, 2020):

Instead of listing them, just put links to the views.
For example, if I have 100 IPs and 20 devices with the same tag, just put a link to /ipam/ip-addresses/?q=&tag=TAG and dcim/devices/?q=&tag=TAG
It will help us to remember what objects are tagged

@Tavoons commented on GitHub (Aug 27, 2020): Instead of listing them, just put links to the views. For example, if I have 100 IPs and 20 devices with the same tag, just put a link to `/ipam/ip-addresses/?q=&tag=TAG` and `dcim/devices/?q=&tag=TAG` It will help us to remember what objects are tagged
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@exokernel commented on GitHub (Sep 8, 2020):

@jeremystretch

This is because listing various types of objects together often doesn't make sense. Each model has its own set of attributes that help uniquely distinguish it to the user, and these are impossible to combine in a single table.

I'm really curious as to why this was possible in 2.8 but no longer in 2.9? Was it just extremely inefficient in 2.8 and therefor dropped? Did something change with the models that actually makes it impossible? This was a really nice feature of 2.8 that's now missing. :(

@exokernel commented on GitHub (Sep 8, 2020): @jeremystretch > This is because listing various types of objects together often doesn't make sense. Each model has its own set of attributes that help uniquely distinguish it to the user, and these are impossible to combine in a single table. I'm really curious as to why this was possible in 2.8 but no longer in 2.9? Was it just extremely inefficient in 2.8 and therefor dropped? Did something change with the models that actually makes it impossible? This was a really nice feature of 2.8 that's now missing. :(
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 9, 2020):

Was it just extremely inefficient in 2.8 and therefor dropped?

It was both inefficient an uninformative, because the list displayed no additional information about each object.

@jeremystretch commented on GitHub (Sep 9, 2020): > Was it just extremely inefficient in 2.8 and therefor dropped? It was both inefficient an uninformative, because the list displayed no additional information about each object.
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@robbagithub commented on GitHub (Sep 10, 2020):

So if you don't know what object has the tag "xyz" then you have to search each object type to find it?

This seems exceptionally inefficient. Even if you could add a drop down to show all the tags assigned to each object type that would help manage the tags

@robbagithub commented on GitHub (Sep 10, 2020): So if you don't know what object has the tag "xyz" then you have to search each object type to find it? This seems exceptionally inefficient. Even if you could add a drop down to show all the tags assigned to each object type that would help manage the tags
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@exokernel commented on GitHub (Sep 10, 2020):

@jeremystretch

I really think this feature needs to come back and it seems I'm not the only one. Personally, I don't care if the query takes a really long time to run or if no information beyond the object type is displayed for each object. We just need a simple way to find all the objects that have a given tag, without having to look through every single object type. If each object in the result set is a link to the view of that object then that's really all we need, I think. There may be other issues I'm not considering but it seems like a desirable feature of any tagging system. Anyway, I understand your reasoning for taking this away and I won't belabor the point further. You're doing great work and Netbox is amazing. I am just really sad to see this missing from 2.9. I used it a lot in 2.8. Thanks again for all your hard work.

@exokernel commented on GitHub (Sep 10, 2020): @jeremystretch I really think this feature needs to come back and it seems I'm not the only one. Personally, I don't care if the query takes a really long time to run or if no information beyond the object type is displayed for each object. We just need a simple way to find all the objects that have a given tag, without having to look through every single object type. If each object in the result set is a link to the view of that object then that's really all we need, I think. There may be other issues I'm not considering but it seems like a desirable feature of any tagging system. Anyway, I understand your reasoning for taking this away and I won't belabor the point further. You're doing great work and Netbox is amazing. I am just really sad to see this missing from 2.9. I used it a lot in 2.8. Thanks again for all your hard work.
adam commented 2025-12-29 18:32:44 +01:00
Author
Owner
Copy Link

@robbagithub commented on GitHub (Sep 10, 2020):

I opened a feature request with a few ideas in there today #5121 https:/
https://github.com/netbox-community/netbox/issues/5121
/github.com/netbox-community/netbox/issues/5121
https://github.com/netbox-community/netbox/issues/5121

On Thu, 10 Sep 2020 at 15:55, exokernel notifications@github.com wrote:

@jeremystretch https://github.com/jeremystretch

I really think this feature needs to come back and it seems I'm not the
only one. Personally, I don't care if the query takes a really long time to
run or if no information beyond the object type is displayed for each
object. We just need a simple way to find all the objects that have a given
tag, without having to look through every single object type. If each
object in the result set is a link to the view of that object then that's
really all we need, I think. There may be other issues I'm not considering
but it seems like a desirable feature of any tagging system. Anyway, I
understand your reasoning for taking this away and I won't belabor the
point further. You're doing great work and Netbox is amazing. I am just
really sad to see this missing from 2.9. I used it a lot in 2.8. Thanks
again for all your hard work.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/netbox-community/netbox/issues/5057#issuecomment-690004500,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFI7FKXWYJLTQUMY6GWCFLTSFBS5ZANCNFSM4QMZJA3A
.

@robbagithub commented on GitHub (Sep 10, 2020): I opened a feature request with a few ideas in there today #5121 https:/ <https://github.com/netbox-community/netbox/issues/5121> /github.com/netbox-community/netbox/issues/5121 <https://github.com/netbox-community/netbox/issues/5121> On Thu, 10 Sep 2020 at 15:55, exokernel <notifications@github.com> wrote: > @jeremystretch <https://github.com/jeremystretch> > > I really think this feature needs to come back and it seems I'm not the > only one. Personally, I don't care if the query takes a really long time to > run or if no information beyond the object type is displayed for each > object. We just need a simple way to find all the objects that have a given > tag, without having to look through every single object type. If each > object in the result set is a link to the view of that object then that's > really all we need, I think. There may be other issues I'm not considering > but it seems like a desirable feature of any tagging system. Anyway, I > understand your reasoning for taking this away and I won't belabor the > point further. You're doing great work and Netbox is amazing. I am just > really sad to see this missing from 2.9. I used it a lot in 2.8. Thanks > again for all your hard work. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/netbox-community/netbox/issues/5057#issuecomment-690004500>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AFI7FKXWYJLTQUMY6GWCFLTSFBS5ZANCNFSM4QMZJA3A> > . >
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
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#4033
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?