[ZBXNEXT-4557] Support edit/add/remove tag from triggers created by trigger prototypes Created: 2018 May 16 Updated: 2018 Nov 27 Resolved: 2018 Nov 27 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Server (S) |
| Affects Version/s: | 3.4.9, 4.0.0alpha6 |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | finalbeta | Assignee: | Unassigned |
| Resolution: | Workaround proposed | Votes: | 2 |
| Labels: | frontend, triggers, usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Currently one can change/add/remove tags on triggers if the trigger was added directly on the host and if it was added through a template. You cannot change/add/remove tags on triggers if the trigger was added through a discovery rule (as a trigger prototype). It would be handy if this functionality would be added as this would add more granularity to triggers. |
| Comments |
| Comment by richlv [ 2018 Nov 24 ] |
|
As discussed on IRC, it would be great to check whether usermacro context solves this need. |
| Comment by finalbeta [ 2018 Nov 27 ] |
|
Hey Richlv. In my use case, the macro name is always the same across all triggers, using user macro context is a working solution. (In practice, I find it too complex as the context could be very long/complex and the value is 0 or 1. I implemented two triggers and I enable the one I need). I can imagine other use cases where one needs to be flexible about the tag names to add to triggers, in that case I wouldn't see a work around. (But as is, my use case has a working workaround, and the amount of work that this change would require would probably be big, thus, I'll check if I can close this.) |