configuration_triggers.jpg
screens.jpg
[ZBXNEXT-746] Trigger severity sorting Created: 2011 Apr 13 Updated: 2011 Dec 22 Resolved: 2011 Jun 21 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Frontend (F) |
| Affects Version/s: | 1.9.3 (alpha) |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Major |
| Reporter: | Alexander Vladishev | Assignee: | Konstantin Buravcov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
configuration_triggers.jpg
screens.jpg
|
| Description |
|
The sort criteria for screen element "status of triggers" shall be optionally configurable in screen-edit to sort by date (desc), host (asc) or severity (higher severities first) It shall also show the number of triggers active, as currently only the first (configured) are shown. Something like "10 of 947 problems". If sorting is not set, it will be sorted as in 1.8.x. Otherwise it should be sorted by selected sorting criteria. Sorting criteria should be displayed but cannot be changed by user, i.e. must be not clickable. |
| Comments |
| Comment by Konstantin Buravcov (Inactive) [ 2011 Jun 08 ] |
|
Proposed DB changes in table screens_items: FIELD |sort_triggers |t_integer |'0' |NOT NULL |ZBX_SYNC 0 - by date DESC Patches and schema are avalable in dev branch |
| Comment by Konstantin Buravcov (Inactive) [ 2011 Jun 09 ] |
|
Done in dev branch |
| Comment by Konstantin Buravcov (Inactive) [ 2011 Jun 14 ] |
|
Merged to trunk rev 20211 |
| Comment by richlv [ 2011 Jun 17 ] |
|
(7) xml import fails : "XML file contains errors. Error 26: Element screenitem has extra content: sort_triggers [ Line: 19 | Column: 0 ]" (8) at least in opera, sorting arrows in header appear to be clickable (cursor changes), but are not. not sure whether it's opera problem or something more generic <KB> Fixed in |