Multiple customer sites have lost access to Support tickets
Incident
Report for Atlassian Developer
Resolved
The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.
Update
Customers continue to encounter a permission error when accessing tickets: No Access - You do not have permission to view this request.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team is engaged and continues investigation. However, the root cause remains unclear. We will provide next update in 3 hours or sooner.
Update
Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team continues investigating. The root cause remains unclear. We will provide next update in 60 minutes.
Update
Customers encounter a permission error when accessing tickets: No Access - You do not have permission to view this request.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team continues investigating. The root cause remains unclear.
We will provide next update in 60 minutes.
Ticket creation works and created tickets are visible to the Atlassian teams.
The Atlassian team continues investigating. The root cause remains unclear.
We will provide next update in 60 minutes.
Investigating
We are aware that access to created Ecohelp support tickets is not available for some of our customers. Our team is investigating this issue.
Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams.
We will provide next update in 60 minutes.
Repeat creation of tickets is not required as the created tickets are visible to the Atlassian teams.
We will provide next update in 60 minutes.
This incident affected: APIs (Bitbucket Cloud APIs, Confluence Cloud APIs, Jira Cloud APIs, Product Events, User APIs, Webhooks, Web Triggers), Marketplace (App listing management, App listings, App pricing, App submissions, Category landing pages, Evaluations and purchases, In-product Marketplace and app installation (Cloud), In-product Marketplace and app installation (Server), Notifications, Private listings, Reporting APIs and dashboards, Search, Vendor management, Vendor Home Page), Developer (App Deployment, Artifactory (Maven repository), Create and manage apps, Developer documentation, Forge App Installation, Forge CDN (Custom UI), Forge Function Invocation, aui-cdn.atlassian.com, Forge App Logs, Forge App Monitoring, Developer console, Forge direct app distribution, Hosted storage, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL), Support (Atlassian Support contact form, Developer community, Developer service desk, Marketplace service desk, Atlassian Support, Vulnerability management [AMS]), and Authentication and user management.