Atlassian incident · via Jira Service Desk
Customers are receiving message NO SUCH TRACK intermittently when opening Jira issues
Resolved after 2 hours 45 minutes, affecting Jira Service Management Web and Service Portal and 1 more, on November 18, 2025.
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.
Affected components
Update timeline
- 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.
- 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.
- 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.
Your product runs on more than Atlassian
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services