-
Incident report
-
Resolution: Unresolved
-
Trivial
-
None
-
7.2.6rc1
-
None
-
Support backlog
Steps to reproduce:
1. Configure a Jira media type in Zabbix 7.2 using the official webhook script.
2. Trigger an event in Zabbix that results in a ticket update (e.g., change of summary or priority).
3. Observe that the update is correctly applied in Jira (e.g., issue summary changes to [RESOLVED] ...).
4. However, no comment is added to the ticket.
Result:
The issue is updated (confirmed in Jira).
Zabbix logs an error:
Failed to parse response: not well-formed JSON was received
No comment is added to the issue.
Additional info:
Template for Zabbix 6.X used payload like:
{ "body":"Problem has been resolved in 3m 0s at 12:07:59 on 2025.04.15" }
and this is producing expected comment in the ticket, all good here.
New (7.2) template uses:
{ "fields": { "summary": "[RESOLVED] httpd.service: Service is not running", "priority": { "name": "P2" } } }
so Zabbix is re-sending again the priority and updating the ticket summary from PROBLEM to RESOLVED, which works again as expected, even if the next line is
[Jira Webhook] notification failed: Failed to parse response: not well-formed JSON was received
so the changes are done, but Zabbix is considering it as a failure for whatever reason (because there is no further response from Jira? maybe…)