Jira Service Management incident

Customers are receiving message NO SUCH TRACK intermittently when opening Jira issues

Major Resolved View vendor source →

Jira Service Management experienced a major incident on November 18, 2025 affecting Jira Service Management Web and Service Portal and 1 more component, lasting 2h 45m. The incident has been resolved; the full update timeline is below.

Started
Nov 18, 2025, 02:43 PM UTC
Resolved
Nov 18, 2025, 05:29 PM UTC
Duration
2h 45m
Detected by Pingoru
Nov 18, 2025, 02:43 PM UTC

Affected components

Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignup

Update timeline

  1. investigating Nov 18, 2025, 02:43 PM UTC

    We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.

  2. monitoring Nov 18, 2025, 03:23 PM UTC

    Impact Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities. Current Status We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident. Next Steps Further updates will be communicated in 60 minutes.

  3. resolved Nov 18, 2025, 05:29 PM UTC

    On November 18, 2025, some Jira Service Management users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.