[ZBX-25314] After the update from 7.0.3 to 7.0.4, integration with Jira Service Desk stopped working. Created: 2024 Sep 30  Updated: 2024 Nov 19  Resolved: 2024 Oct 13

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 7.0.4
Fix Version/s: 7.0.5rc1, 7.2.0alpha1

Type: Problem report Priority: Critical
Reporter: Post Zabbix User Assignee: Andrew Biba
Resolution: Fixed Votes: 2
Labels: Integration, Server, integration, server, updateproblem
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

[root@helpdesk ~]# cat /etc/redhat-release
AlmaLinux release 8.10 (Cerulean Leopard)

[root@helpdesk ~]# rpm -qa|grep zabbix
zabbix-apache-conf-7.0.4-release1.el8.noarch
zabbix-web-7.0.4-release1.el8.noarch
zabbix-sql-scripts-7.0.4-release1.el8.noarch
zabbix-web-deps-7.0.4-release1.el8.noarch
zabbix-server-pgsql-7.0.4-release1.el8.x86_64
zabbix-release-7.0-5.el8.noarch
zabbix-web-pgsql-7.0.4-release1.el8.noarch
zabbix-selinux-policy-7.0.4-release1.el8.x86_64
zabbix-agent2-7.0.4-release1.el8.x86_64

[root@helpdesk ~]# rpm -qa|grep httpd
httpd-filesystem-2.4.37-65.module_el8.10.0+3874+c2064c23.2.noarch
almalinux-logos-httpd-84.5-1.el8.noarch
httpd-tools-2.4.37-65.module_el8.10.0+3874+c2064c23.2.x86_64
httpd-2.4.37-65.module_el8.10.0+3874+c2064c23.2.x86_64

[root@helpdesk ~]# rpm -qa|grep php
php-pdo-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-gd-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-common-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-bcmath-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-pgsql-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-ldap-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-xml-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-fpm-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64
php-mbstring-8.2.13-1.module_el8.10.0+3796+30ed3ef7.x86_64

[root@helpdesk-db ~]# rpm -qa|grep postgres
postgresql15-server-15.8-1PGDG.rhel8.x86_64
postgresql15-contrib-15.8-1PGDG.rhel8.x86_64
postgresqltuner-1.0.1-4.el8.noarch
postgresql15-libs-15.8-1PGDG.rhel8.x86_64
postgresql15-15.8-1PGDG.rhel8.x86_64

NO TimescaleDB - DB not partitioning

Attachments: PNG File image-2024-09-30-09-50-53-964.png     PNG File image-2024-09-30-09-56-05-858.png     PNG File image-2024-09-30-10-05-01-937.png     Text File zabbix-704--error.txt    
Issue Links:
Causes
caused by ZBX-24636 {HOST.IP} and {HOST.DNS} not blank if... Closed
Duplicate
is duplicated by ZBX-25318 Solarwinds integration failing with 4... Closed
Sprint: S24-W40/41
Story Points: 0.5

 Description   

Steps to reproduce:

  1. Fresh installation of Zabbix version 6.0.34 or 7.0.2 or 7.0.3
    Use of official integration with Jira ServiceDesk

https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/media/jira_servicedesk?at=release/7.0

Integration WORKS.

  1. Update to version 7.0.4 - integration stops working.
    Absolutely no changes were made to the Jira Service Desk environment.

Result:

Integration with Jira ServiceDesk does not work after updae to 7.0.4

See screenshot...
See log file...

Expected:

Integration with Jira ServiceDesk should work after upgrading to version 7.0.4

 Comments   
Comment by Post Zabbix User [ 2024 Sep 30 ]

I made a small comparison of what features work in the official integration of Zabbix with Jira Service Desk when they worked and when it stopped working.

Comment by Evgeny Yurchenko [ 2024 Sep 30 ]

In 7.0.3 if MACRO is not defined it is passed to the Media script as

"jira_request_key":"{EVENT.TAGS.__zbx_jira_requestkey}"

In 7.0.4 if MACRO is not defined it is passed to the Media script as

"jira_request_key":"*UNKNOWN*"
Comment by Evgeny Yurchenko [ 2024 Sep 30 ]

Looks like commit ad1f40b97ed is to blame.

Comment by Alexander Vladishev [ 2024 Sep 30 ]

Currently (in version 7.0.4), these macros are now expanding correctly, just like all other built-in macros. However, we didn’t account for the fact that integrations are tied to the old macro behavior.

We will fix the integrations as soon as possible so that you can download them.

Alternatively, you can replace "{EVENT.TAGS.__zbx_jira_requestkey}" with "*UNKNOWN*" in the Jira ServiceDesk media type's JavaScript.

Comment by Evgeny Yurchenko [ 2024 Sep 30 ]

> Alternatively, you can replace "{EVENT.TAGS.__zbx_jira_requestkey}" with "UNKNOWN" in the Jira ServiceDesk media type's JavaScript.
this is exactly what we did to fix the issue. Thanks.

Comment by Aleksandr Iantsen [ 2024 Oct 02 ]

Fixed in:

Comment by Marianna Zvaigzne [ 2024 Oct 07 ]

Documentation updated: 

Generated at Sun Apr 20 20:33:28 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.