Atlassian Developer incident

Multiple customer sites have lost access to Support tickets

Minor Resolved View vendor source →

Atlassian Developer experienced a minor incident on December 5, 2025 affecting Bitbucket Cloud APIs and App listing management and 1 more component, lasting 4h. The incident has been resolved; the full update timeline is below.

Started
Dec 05, 2025, 08:08 AM UTC
Resolved
Dec 05, 2025, 12:09 PM UTC
Duration
4h
Detected by Pingoru
Dec 05, 2025, 08:08 AM UTC

Affected components

Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage apps

Update timeline

  1. investigating Dec 05, 2025, 08:08 AM UTC

    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.

  2. investigating Dec 05, 2025, 09:23 AM UTC

    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.

  3. investigating Dec 05, 2025, 09:56 AM UTC

    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.

  4. investigating Dec 05, 2025, 11:06 AM UTC

    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.

  5. resolved Dec 05, 2025, 12:09 PM UTC

    The feature flag causing the issue has been reverted, fixing the problem. With that this incident is resolved.