-
Problem report
-
Resolution: Fixed
-
Blocker
-
6.4.0beta3
-
None
-
Sprint 95 (Dec 2022), Sprint 96 (Jan 2023), Sprint 97 (Feb 2023), Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023), Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023), Sprint 107 (Dec 2023), S2401
-
2
As initially reported issue in ZBX-21009 has evolved, it turned out that adding backslash escaping to the function parameters of history functions would break:
- triggers that have backslashes in history functions parameters
- calculated items that have backslashes in history functions parameters
As such it was decided to roll back changes made in ZBX-21536 and /ZBX-21534 on all branches except on master.
It was decided, going forward, that Zabbix should have proper backslash escaping in parameters of history functions.
- causes
-
ZBX-25265 "regsub" macro function duplicates forward slashes when output part is put in double quotes
- Closed
-
ZBX-23617 Test item cannot find macro if specified in quotes but on server it works
- Closed
- depends on
-
ZBX-23318 front-end allows to enter unescaped single backslash in replace preprocessing
- Closed
- is duplicated by
-
ZBX-21856 trigger / calculated expression regexp dot escape possible regression
- Closed
-
ZBX-21998 Zabbix 6 regexp: incorrect expression "6\.2"
- Closed
- part of
-
ZBX-22149 Trigger upgrade issue
- Closed