Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-25314

After the update from 7.0.3 to 7.0.4, integration with Jira Service Desk stopped working.

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Fixed
    • Icon: Critical Critical
    • 7.0.5rc1, 7.2.0alpha1
    • 7.0.4
    • Templates (T)
    • S24-W40/41
    • 0.5

      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

        1. image-2024-09-30-09-50-53-964.png
          image-2024-09-30-09-50-53-964.png
          25 kB
        2. image-2024-09-30-09-56-05-858.png
          image-2024-09-30-09-56-05-858.png
          155 kB
        3. image-2024-09-30-10-05-01-937.png
          image-2024-09-30-10-05-01-937.png
          79 kB
        4. zabbix-704--error.txt
          15 kB

          [ZBX-25314] After the update from 7.0.3 to 7.0.4, integration with Jira Service Desk stopped working.

          Post Zabbix User added a comment - - edited

          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.

          Post Zabbix User added a comment - - edited 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.

          Evgeny Yurchenko added a comment - - edited

          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*"

          Evgeny Yurchenko added a comment - - edited 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*"

          Evgeny Yurchenko added a comment -

          Looks like commit ad1f40b97ed is to blame.

          Evgeny Yurchenko added a comment - Looks like commit ad1f40b97ed is to blame.

          Alexander Vladishev added a comment -

          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.

          Alexander Vladishev added a comment - 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.

          Evgeny Yurchenko added a comment -

          > 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.

          Evgeny Yurchenko added a comment - > 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.

          Aleksandr Iantsen added a comment -

          Fixed in:

          Aleksandr Iantsen added a comment - Fixed in: 7.0.5rc1 61cf512691d 7.2.0alpha1 (master) 094e5ad4eeb

          Marianna Zvaigzne added a comment -

          Documentation updated: 

          Marianna Zvaigzne added a comment - Documentation updated:  Installation > Upgrade notes ( 7.0.0 , 7.0.4 )

            abiba Andrew Biba
            postowy-zabbix Post Zabbix User
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: