[ZBXNEXT-1337] don't allow to choose unusable triggers for dependencies Created: 2009 Feb 27 Updated: 2012 Oct 13 |
|
| Status: | Reopened |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F) |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Change Request | Priority: | Minor |
| Reporter: | richlv | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | dependencies, trigger, trivial, usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
adding a trigger as a dependency that already is added should either produce warning, or, ideally, this trigger should not appear in the list to select at all. currently it is allowed to select such a trigger, but it mysteriously is skipped. additionally, it is possible to add trigger as depending on itself. it only produces error upon saving, not upon adding. ideally such triggers would not appear in lists to select at all, or they would appear, but greyed out |
| Comments |
| Comment by Alexei Vladishev [ 2012 Jul 28 ] |
|
Such issues will be fixed eventually. It is more usability related problem not a bug per se. |
| Comment by richlv [ 2012 Jul 28 ] |
|
well, it's not consistent (works ok with maps), so that's a bug right there. nevertheless, it's a zbxnext as a minimum... |