Jira Software Outage History

Jira Software users relying on the GitHub for Jira Connector experienced degraded data pipelines, with missing pull requests and other data synchronization issues. The Create and Edit component was affected, leading to incomplete data in Jira from GitHub. The incident began on May 15, 2025 2:24 AM UTC and was resolved on May 20, 2025 12:59 AM UTC, lasting about 4 days, 22 hours, and 35 minutes. The status page issued two updates during the incident, first noting an investigation and later confirming resolution.

Jira Software experienced partial unavailability in managing Forge apps across Atlassian platforms, impacting app lifecycle operations (installations and removals), developer console usage (including tunneling), and Forge app creation and deployment. Users could have faced difficulties performing Forge-related tasks, with the Marketplace component showing degraded behavior during the incident. The outage lasted about 46 minutes, beginning at 12:59 PM UTC and resolving by 1:45 PM UTC.

The Jira Software team issued two status updates during the incident, identifying the root cause and confirming mitigations were in progress as services returned to normal.

Jira Software reported degraded performance in automation rule execution, impacting Automation for Jira across Confluence, Jira Work Management, Jira Service Management, Jira, and Jira Product Discovery Cloud customers. During the incident, automated workflows and rule-triggered actions could be delayed. The outage began at Apr 23, 2025 2:18 PM UTC and was resolved by Apr 23, 2025 11:39 PM UTC, lasting about 9 hours and 21 minutes. The provider issued 2 official status updates during the incident.

The Sprint field was not visible in Jira Software issues, and sprint values shown in issue search and filters were blank for all Jira Software customers. This degraded sprint-based planning and issue discovery, affecting users' ability to view or filter work by sprint. The outage began on Apr 18, 2025 4:24 AM UTC and was resolved by Apr 22, 2025 1:54 PM UTC, lasting roughly 4 days and 9 hours. The Jira Software status page issued two official updates during the incident and confirmed a root cause with a plan for recovery, followed by full restoration.

The Jira Software team experienced issues loading Dashboard widgets, impacting the Jira Dashboard experience for users. The problem affected the Viewing content component and caused dashboards to fail rendering for a period of time. The outage began at 6:59 AM UTC and lasted approximately 16 hours, with service returning to normal by 10:59 PM UTC. Jira Software issued 2 status updates during the incident as they investigated and worked toward resolution.

Jira Software experienced a partial outage affecting the Assets viewing experience in some regions. Users attempting to view Assets reported an error such as 'there is a problem loading the objects,' preventing access to Asset data.

The incident began on Apr 16, 2025 12:14 AM UTC and was resolved by Apr 16, 2025 1:09 AM UTC, lasting about 55 minutes. The Jira Software team issued two status updates during the incident, and the issue was resolved once the affected components returned to normal. The problem was tied to the Viewing content component.

Jira users attempting to load the Administration page across Atlassian products encountered a blank screen, blocking access to admin settings. The incident began at 12:39 AM UTC and lasted until 1:34 AM UTC, with the Administration component listed as down during the outage.

The Atlassian status page provided two updates during the incident: first at 12:37 AM UTC noting Investigating, and a follow-up at 1:34 AM UTC indicating the Administration service was restored. The outage affected the Admin UI across Atlassian products and disrupted administrative workflows.

Jira Software experienced regional access issues that prevented some users from loading Jira sites. The incident affected 11 components across Jira services, including Purchasing & Licensing, Mobile, Signup, Notifications, Administration, Viewing content, Marketplace, Search, Automation for Jira, Create and edit, and Authentication and User Management, with reports concentrated in certain regions.

The outage began at 5:44 AM UTC and was resolved by 6:40 AM UTC, lasting approximately 56 minutes. Jira's status page showed the issue was first listed as investigating before the incident was resolved, and the page posted two updates during the event.

Jira Software users experienced a brief degradation affecting the Team field in the issue view across Jira Work Management, Jira Service Management, and Jira projects. Users were unable to view or assign the Team field value in issues, disrupting typical workflows for a subset of customers. The problem was isolated to the Create and edit component of the issue view.

The incident began around 5:07 PM UTC and lasted about 5:59 PM UTC (roughly 52 minutes). The Jira status page showed two updates during the event: an initial investigation at Mar 24, 2025 5:09 PM UTC and a final resolution at Mar 24, 2025 5:59 PM UTC, after which the issue returned to normal.

Some Jira customers were unable to view or assign teams from the team field dropdown, impacting the Create and edit component across Jira Work Management, Jira Service Management, and Jira. The issue began at Mar 19, 2025 10:10 PM UTC and was resolved by Mar 20, 2025 6:44 AM UTC, lasting approximately 8 hours and 34 minutes. The Jira status page issued 2 updates during the incident.

The first update indicated an investigation into the issue and later confirmed that the team field visibility and assignment were restored, with the service returning to normal after the final update.