[ZBX-5833] Trigger expression constructor does not work correctly Created: 2012 Nov 09  Updated: 2017 May 30  Resolved: 2012 Dec 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.15, 2.0.3
Fix Version/s: 1.8.16rc1, 2.0.4rc1, 2.1.0

Type: Incident report Priority: Major
Reporter: Kodai Terashima Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: frontend, triggers, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1.8-after.png     PNG File 1.8-before.png     PNG File 2.0-after.png     PNG File 2.0-before.png    
Issue Links:
Duplicate

 Description   

Trigger expression condtructor doesn't work correctly in 1.8.15 and 2.0.3.

Macro cannot insert to expression under some conditions in 1.8.15, and constructor tree is broken when "or" operator is used in 2.0.



 Comments   
Comment by Oleg Egorov (Inactive) [ 2012 Nov 21 ]

Problem exist only in 2.0.4.
In 2.1 and DEV-522 this issue cannot reproduce.

Comment by Alexander Vladishev [ 2012 Nov 23 ]

Fixed in pre-2.0.4 r31650 and pre-2.1.0 r31649.

Comment by Alexander Vladishev [ 2012 Nov 23 ]

Fixed under DEV-522 (simplifying of trigger expression parser).

Comment by Alexander Vladishev [ 2012 Nov 28 ]

Reopening to fix in 1.8.x.

Comment by Kodai Terashima [ 2012 Nov 28 ]

This problem is reproducible in 1.8.15.

If the second expression has

{TRIGGER.VALUE}

=0 macro (1.8-before.png), the constructor is broken like 1.8-after.png after inserting new macro.

Comment by Alexander Vladishev [ 2012 Dec 07 ]

Fixed with ZBX-5884 in version pre-1.8.16 r31955

Comment by richlv [ 2012 Dec 08 ]

i believe this one can be closed - please reopen if not

Generated at Fri Apr 19 21:42:55 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.