Summary

On July 23, 2026 from 20:42 UTC to 21:31 UTC , some customers using the Jira v1 integration experienced an issue where updates made in Jira did not appear in their linked Zendesk tickets. Other parts of the integration continued to work, but field updates were not completing as expected.
 

Root Cause Analysis

This incident was caused by a recent platform upgrade in the Jira integration service. During the update, an internal component it relied on was no longer available, which caused background tasks to stop completing properly. As a result, field updates were left unfinished. Because the issue happened behind the scenes, it did not produce clear signs of failure, which made it look like the updates were just stuck.
 

Resolution

To fix this issue, we returned the Jira integration service to the previous version that was working as expected. This restored normal processing and allowed updates to complete again. 
 

Remediation Items

To reduce the likelihood of this happening again, we are taking steps including:

  1. Improve alerting for silent job failures
    Add monitoring that detects when background jobs are failing without producing explicit errors or queue growth.

  2. Restore and strengthen integration smoke tests
    Re-enable Jira integration smoke tests with valid test accounts so field-sync failures are caught before production release.

  3. Add safer dependency upgrade checks
    Improve validation for framework upgrades to detect when removed methods or incompatible instrumentation could affect job processing.

  4. Enhance observability for field sync processing
    Add clearer metrics and logs for job pickup, completion, and failure states so stuck syncs can be identified sooner.

  5. Review SLO/SLI coverage for field sync behavior
    Ensure current reliability measurements capture silent failures, not just queue size or explicit error conditions.
     

FOR MORE INFORMATION

For current system status information about Zendesk and specific impacts to your account, visit our system status page. If you have additional questions about this incident, contact Zendesk customer support.

Powered by Zendesk