-
New Feature Request
-
Resolution: Fixed
-
Trivial
-
2.2.10
-
Team B
-
Sprint 69 (Oct 2020), Sprint 70 (Nov 2020), Sprint 71 (Dec 2020), Sprint 72 (Jan 2021), Sprint 73 (Feb 2021), Sprint 74 (Mar 2021), Sprint 75 (Apr 2021), Sprint 76 (May 2021), Sprint 77 (Jun 2021)
-
10
How about supporting tags or key words in configuration entities like hosts, items, triggers, graphs, maps, screens and possibly more?
Such tags may provide contextual information, extend frontend filtering as well as action conditions with a flexible option.
The idea is certainly not new as some sort of tagging can be found in many applications nowadays.
I see also similarities with ZBXNEXT-336, ZBXNEXT-577, ZBXNEXT-1645, ZBXNEXT-2087 and possibly more. Maybe it's even a duplicate.
- causes
-
ZBXNEXT-4731 Host and template level tags
-
- Closed
-
-
ZBX-24088 Map hierarchy ignores tag filters
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- part of
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
