We often use two host tag groups to classify hosts more accurately. The 1st one is “system class”, the 2nd one is “system type”. In “system class” you will find tags like “Server, Router, Switch, Firewall” etc (more like an overall classification). In “system type” you then will find tags like “DNS Server, Domain Controller, …, Core Switch, Access Switch, …” (specializing the overall classification to more detail).
The problem is: At the moment the admin can configure a host with the tags “system class” --> “Server” and “system type” --> “Access Switch” - which obviously is nonsens.
The idea: Introduce the (optional!) ability to make tag groups dependent from each other in the following way: Selecting an entry in the 1st one would lead to only a subset of entries in the 2nd one.
Example to clarify (based on the examples given above):
Selecting “Switch” from the “system class” tag group would lead to only have the following options available when choosing from the tag group “system type” when configuring a host: “Core Switch” or “Access Switch”.
IMHO the logic is not that complicated - but honestly I have no idea how to present the dependency creation options to the admin within the UI…
Maybe using of corresponding prefixes to the tag IDs in such dependent tag groups would be a very initial idea.
Ralf from Germany, on a very rainy and cold day