Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the ability to do global search by tags #16181

Open
BrunoBlanes opened this issue May 17, 2024 · 2 comments
Open

Add the ability to do global search by tags #16181

BrunoBlanes opened this issue May 17, 2024 · 2 comments
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application

Comments

@BrunoBlanes
Copy link
Contributor

BrunoBlanes commented May 17, 2024

NetBox version

v4.0.2

Feature type

New functionality

Proposed functionality

Add a field to select one or more tags and filter results by them, even when no query is given, and make it work with the existing search fields in a way that one could look up only objects that match all specified tags and are of a specific object type.
image

Use case

Tags are useful for sorting objects into categories, for example, I set the same tag to all objects that are allocated to a specific client, IP, Prefix, VLAN, etc., let's call that tag 13500, which represents the client's ID on my ERP. I currently have a couple of integrations which do use tags to identify objects.

By having the ability to search, globally, by tags, I can find the resources of said category faster, without the need to dive into every object menu.

The tags menu isn't that well invested and so it does not return much information about the object and does not allow me to filter by objects with multiple tags as parameter.

Database changes

None as far as I could guess since this is just a search and UI improvement, maybe some new indexing.

External dependencies

None.

@BrunoBlanes BrunoBlanes added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels May 17, 2024
@abhi1693 abhi1693 added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: needs triage This issue is awaiting triage by a maintainer labels May 17, 2024
@Mailstorm-ctrl
Copy link

You might benefit more from custom fields than this functionality. Custom fields will achieve what you are wanting (search by value of custom field).

So what you'd do is create a custom field and assign it to whatever objects you want (or leave blank for everything). So you may do "Client Number" as the field name and then you just input whatever the client number is for that particular object.

However, the proper way to do this is to make a tenant (which I assume you are doing) for every client you have and assign the appropriate objects to that tenant. Then in that Tenant you'd have a custom field for the customer ID in your ERP. That way whenever you go to an object, you can just look at the tenant information then from there get the customer ID.

You'd have to change/modify your integrations but this is the way you'd want to do.

@BrunoBlanes
Copy link
Contributor Author

BrunoBlanes commented May 20, 2024

That would solve the Client ID problem, but Tags can be used for much more than just that, for example, if I'd like to lookup all equipment that is allocated to clients under contract I'd have a tag for that, or IP addresses that are monitored via ICMP, I'd add a tag for that. And then you can start to mix and match tags for advanced filtering.

Tags are easier and more interactive than custom fields, which is not to say they don't have their own use case, for example, we use custom fields under Sites to register the Contract ID for each site with our local power supply company, so in case we have a power outage, we have the right info within Netbox.

@jeremystretch jeremystretch added the complexity: medium Requires a substantial but not unusual amount of effort to implement label May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

5 participants