[ZBX-5278] Change text "All" too "All (monitored)" in a trigger status filter at Triggers page Created: 2012 Jul 05  Updated: 2017 May 30  Resolved: 2012 Jul 26

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.14, 2.0.0
Fix Version/s: None

Type: Incident report Priority: Minor
Reporter: Oleksii Zagorskyi Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: filters, trigger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBXNEXT-892 Triggers should be filterable by Unkn... Open

 Description   

This issue is addressed for cases when an item used in a trigger expression is in not supported state for some reason and user see at the Triggers/Overview pages.
Users expect that they will see all triggers (without exceptions) at the Triggers page if they select "All" in the filter, but it's a bit not true.

So to bring some idea that "All" has some exception I'm suggesting to change this text to "All (monitored)" or similar.
It will clarify GUI behavior a bit.

The same behavior related to an Overview page, but there no any filters, so it does not mislead as the Triggers page does.



 Comments   
Comment by richlv [ 2012 Jul 05 ]

this might be still confusing, as triggers are not 'monitored'...
and unsupported items are still being monitored as well.

<richlv> if we do this, then the best option probably would be to change the dropdown label to something like "Triggers, referencing enabled items"
ugly, long, creating more work for translators but at least correct

(well, best actually would be those helper icons where we could provide more info, but meh)

zalex, do you think such a label would help users ?

<zalex> The last suggestion sounds good. I think that 4 words length it's NOT a problem at all. Compare please with labels for "Acknowledge status", there are 3,4 words length strings and they are ok.
I'm sure that an a bit long and clear string is much better than short&unclear one.
Then we could change also a "Problem" label to something more .... hmm .... "wide"(extended) if you like, but it's an option .

and please ignore extra work for translators, it's a minor issue

<zalex> also, as it is a status, probably this version would be correct "Any (triggers, referencing enabled items)"

<richlv> i'd prefer avoiding status, as ok/problem is also status...

<zalex> hey, maybe we could add a 3rd label - all without exceptions, i.e. including disabled/notsupported triggers ?
I suppose it would be useful and clear (with new corresponding strings).

<richlv> and filters for unknown and ok triggers, and... well, all that will have to go in zbxnexts

<Vedmak> so, is there decision on what need to be changed?

<zalex> I'm afraid my last suggestion leads to a new ZBXNEXT (which means no chances that it will be implemented)
So I don't know what to do. Probably we need more opinions.

<richlv> for this issue, i'd go with "Triggers, referencing enabled items" label change only

Comment by Alexey Fukalov [ 2012 Jul 17 ]

dev branch: svn://svn.zabbix.com/branches/dev/ZBX-5278

Comment by Oleksii Zagorskyi [ 2012 Jul 17 ]

(1) about the dev branch: hmm, looks interesting.
You changed a description of the drop-down but not the "All" entry itself.
I'm not sure it's the same what Rich meant.

<pavels> I don't think the fix in the dev branch will do: it's completely unclear what does it mean and what does it have to do with the dropdown.

<richlv> we do have similar text and concept elsewhere, for example, see the tooltips in reports -> status of zabbix;
we can't go with "all (monitored)", because we do not have concept of "monitored" triggers (they can be enabled or disabled, and that's it).
what exactly is unclear ? is it the label ?

Comment by Alexey Fukalov [ 2012 Jul 26 ]

To properly resolve this issue we decided to implement changes described in ZBXNEXT-892

Generated at Thu Apr 10 23:17:57 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.