[ZBX-4412] Incorrect event age in "Last 20 issues" Created: 2011 Nov 30 Updated: 2017 May 30 Resolved: 2012 Apr 18 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Frontend (F) |
| Affects Version/s: | 1.9.9 (beta) |
| Fix Version/s: | 2.0.0rc4 |
| Type: | Incident report | Priority: | Blocker |
| Reporter: | Alexey Pustovalov | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dashboard, regression | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
trunk rev 23639 |
||
| Description |
|
after revision 23561, in last 20 issues events show date from adding trigger. |
| Comments |
| Comment by Igor Danoshaites (Inactive) [ 2011 Nov 30 ] |
|
Hi, In v1.9.9, rev #23645, in the "Monitoring->Dashboard->Last 20 issues" report, for the already existing trigger is shown not correct "Last change" date, but in the Events report for this trigger are shown correct dates. |
| Comment by richlv [ 2011 Dec 01 ] |
|
(1) unittest, somewhere |
| Comment by Pavels Jelisejevs (Inactive) [ 2012 Apr 10 ] |
|
This issue has already been fixed in the latest trunk. CLOSED. |
| Comment by Alexander Vladishev [ 2012 Apr 11 ] |
|
Sorting in Last 20 issues should be fixed REOPENED |
| Comment by Alexander Vladishev [ 2012 Apr 18 ] |
|
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-4412 on server side. Now trigger.lastchange field will be updated only by significant events. It should fix the given issue. |
| Comment by dimir [ 2012 May 02 ] |
|
Successfully tested. The fix would skip updating lastchange field in case of unrelevant (e. g. unknown events) trigger status change. |
| Comment by Alexander Vladishev [ 2012 May 03 ] |
|
Fixed in version pre-2.0.0rc4 r27253 |