[ZBX-23398] Trigger expression constructor with disabled expressions shows incorrect "<", ">" signs Created: 2023 Sep 12  Updated: 2024 Jul 01  Resolved: 2024 Jul 01

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 5.0.37, 6.0.21, 6.4.6, 7.0.0alpha5
Fix Version/s: 6.0.32rc1, 6.4.17rc1, 7.0.1rc1, 7.2.0alpha1

Type: Problem report Priority: Trivial
Reporter: Elina Pulke (Inactive) Assignee: Ivo Kurzemnieks
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 2h 8m
Original Estimate: Not Specified

Team: Team B
Sprint: Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), S24-W24/25
Story Points: 1

 Description   

Note! Please fix this only after merge of ZBXNEXT-8453.

Additional escaping in trigger expressions expression table, for example ">"(greater character) is escaped to &gt. This is observed only for triggers with "readonly" expressions.

Steps to reproduce:

  • Open Zabbix server host and click on inherited trigger, "Linux by Zabbix agent: Linux: /etc/passwd has been changed" for example.
  • In trigger popup click "expression constructor"

Observed:
Expression part - 

{{last(/Zabbix server/vfs.file.cksum[/etc/passwd,sha256],#1)&lt;&gt;last(/Zabbix server/vfs.file.cksum[/etc/passwd,sha256],#2)}}

Expected:

Expression do not have double escaping - 

{{last(/Zabbix server/vfs.file.cksum[/etc/passwd,sha256],#1)<>last(/Zabbix server/vfs.file.cksum[/etc/passwd,sha256],#2)}}


 Comments   
Comment by Ivo Kurzemnieks [ 2024 May 27 ]

Fixed in development branches:

Comment by Ivo Kurzemnieks [ 2024 Jun 20 ]

Fixed in:

Generated at Tue Sep 02 23:12:11 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.