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

Offer a Global view for Tagged objects. #2092

New Issue
Closed
opened 2025-12-29 17:22:13 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:22:13 +01:00
Owner
Copy Link

Originally created by @Bill-Irvine on GitHub (Nov 7, 2018).

Environment

  • Python version: 3.5
  • NetBox version: 2.4.6

Proposed Functionality

At the moment we are only able to view tags by object type. i.e. Just circuits or just routers with a specific tag. yet we are able to tag multiple types of object with the same tag.

When clicking a tag we remain within the object that the tag was selected in. I.e if the tag was in circuits then clicking "TESTTAG" would result in https://netbox/circuits/circuits/?tag=TESTTAG

This request is to create a view that allows us to view tags applied to multiple objects similar to how the search function currently looks. The proposed view would list all objects types with that same tag applied.

https://netbox/extras/tags/?tag=TESTTAG

image

In the admin view we are able to see multiple objects with the same tag applied, so making a view with this same functionality shouldn't require any database changes as the functionality looks to already exist.

image

From here we could link the current tags view to a list of all objects under that tag.

image

Or linkable from the object itself that is tagged to see the rest of the objects that have this tag.

image

Use Case

We are looking at implementing tags to track what objects make up a service. This can include interfaces, routers, vlans, sites, etc.

Being able to click on a tag and have all of these tagged objects show up would make this a great visual reference of what objects have been linked together. This could also be used to see what part of a network impacts another part if they are tagged together.

Database Changes

None, this is already viewable under the Taggit page in the admin panel, it should only require a view and url addition.

External Dependencies

None. This will leverage the current Taggit dependency.

Originally created by @Bill-Irvine on GitHub (Nov 7, 2018). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.5<!-- Example: 3.5.4 --> * NetBox version: 2.4.6<!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality At the moment we are only able to view tags by object type. i.e. Just circuits or just routers with a specific tag. yet we are able to tag multiple types of object with the same tag. When clicking a tag we remain within the object that the tag was selected in. I.e if the tag was in circuits then clicking "TESTTAG" would result in https://netbox/circuits/circuits/?tag=TESTTAG This request is to create a view that allows us to view tags applied to multiple objects similar to how the search function currently looks. The proposed view would list all objects types with that same tag applied. https://netbox/extras/tags/?tag=TESTTAG ![image](https://user-images.githubusercontent.com/5893433/48109774-aaf1e800-e2ad-11e8-990d-724c31b38d86.png) In the admin view we are able to see multiple objects with the same tag applied, so making a view with this same functionality shouldn't require any database changes as the functionality looks to already exist. ![image](https://user-images.githubusercontent.com/5893433/48110418-e3df8c00-e2b0-11e8-85ca-ff2e088f674e.png) From here we could link the current tags view to a list of all objects under that tag. ![image](https://user-images.githubusercontent.com/5893433/48110284-0f15ab80-e2b0-11e8-867c-80119be72b87.png) Or linkable from the object itself that is tagged to see the rest of the objects that have this tag. ![image](https://user-images.githubusercontent.com/5893433/48156817-0adea200-e333-11e8-8448-412a82e251c2.png) <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case We are looking at implementing tags to track what objects make up a service. This can include interfaces, routers, vlans, sites, etc. Being able to click on a tag and have all of these tagged objects show up would make this a great visual reference of what objects have been linked together. This could also be used to see what part of a network impacts another part if they are tagged together. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes None, this is already viewable under the Taggit page in the admin panel, it should only require a view and url addition. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None. This will leverage the current Taggit dependency.
adam added the status: acceptedtype: feature labels 2025-12-29 17:22:13 +01:00
adam closed this issue 2025-12-29 17:22:13 +01:00
adam commented 2025-12-29 17:22:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 7, 2018):

To be clear, you're proposing a complete list of all objects assigned to a single tag, correct? As opposed to a view which lists all objects assigned to all tags?

Also, a tangent: The current admin UI should have been removed in the v2.4 release. Manually assigning tagged objects in that manner obviously isn't very user-friendly.

@jeremystretch commented on GitHub (Nov 7, 2018): To be clear, you're proposing a complete list of all objects assigned to a *single* tag, correct? As opposed to a view which lists all objects assigned to all tags? Also, a tangent: The current admin UI should have been removed in the v2.4 release. Manually assigning tagged objects in that manner obviously isn't very user-friendly.
adam commented 2025-12-29 17:22:14 +01:00
Author
Owner
Copy Link

@Bill-Irvine commented on GitHub (Nov 7, 2018):

Correct. A view that shows a complete list of all objects assigned to a single tag.

Although #2558 could be included in this aswell if multiple tags were required.

The admin view was just an example of how this functionality could be seen at the moment. I wont be planning on using this to assign objects to tags going forward.

Thanks.

@Bill-Irvine commented on GitHub (Nov 7, 2018): Correct. A view that shows a complete list of all objects assigned to a single tag. Although #2558 could be included in this aswell if multiple tags were required. The admin view was just an example of how this functionality could be seen at the moment. I wont be planning on using this to assign objects to tags going forward. Thanks.
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#2092
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?