[ZBXNEXT-3425] Create more compact problem view in triggers list, event details and history of events Created: 2016 Sep 07  Updated: 2017 Apr 25  Resolved: 2016 Dec 13

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: None
Fix Version/s: 3.2.2, 3.4.0alpha1, 3.4 (plan)

Type: Change Request Priority: Major
Reporter: Ivo Kurzemnieks Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: eventdetails, problems, screenitem, triggers
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Before implementation of high-performance view of current problems, it was not clear which event closed which event. Now in places like trigger list, event details and screen element history of events the problem still remains. General idea is to make those views same way like it's currently done in Monitoring->Problems view - event and recovery event in one line.

 Comments   
Comment by Ivo Kurzemnieks [ 2016 Nov 07 ]

(1)
Translation string changes:

Strings added:

  • Resolved by

Strings deleted:

  • Generated by

oleg.egorov CLOSED

Comment by Natalja Romancaka [ 2016 Nov 11 ]

(2) Discussed with sasha, decided to add separating rows "Problem" and "Recovery" in event detail widgets "Message actions" and "Command actions" the same like in hint box

iivs RESOLVED in r63729

natalja.zabbix ui tested

gunarspujats CLOSED

Comment by Gunars Pujats (Inactive) [ 2016 Nov 21 ]

(3) As discussed with sasha in Monitoring -> Triggers for all events instead of OK should be RESOLVED, only triggers will have OK status.

iivs RESOLVED in r63868

natalja.zabbix if in filter selected "Show all (7 days)" on Monitoring->Triggers
Invalid argument supplied for foreach() [ in tr_status.php:710]

iivs Somehow, I failed to see an error on page, but still RESOLVED in r63881

gunarspujats CLOSED

Comment by Gunars Pujats (Inactive) [ 2016 Nov 21 ]

(4) As discussed with sasha, in tr_events.php code block for getting eventid if r_eventid is given should be removed

iivs RESOLVED in r63863

gunarspujats CLOSED

Comment by Ivo Kurzemnieks [ 2016 Nov 22 ]

Implemented in:

  • pre-3.2.2rc1 r63896
  • pre-3.3.0 (trunk) r63897
Comment by Martins Valkovskis [ 2016 Nov 30 ]

(5) Updated documentation:

RESOLVED

iivs Looks good to me. If no objections...
CLOSED.

Comment by Alexander Vladishev [ 2017 Mar 13 ]

It caused regressions, see ZBX-11907, ZBX-11981.

Generated at Sat Apr 20 16:35:22 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.