Identified - We have identified that this behavior existed for long time and is due to a bug triggered in edge scenario when following sequence of events happens:
1. First a paid app gets suspended due to lack of payment 2. Then administrator decides to uninstall app 3. Then administrator decides to (re)install app 4. Payment is issued for the app 5. App fails to reactivate (as a result of this bug)
We are advising customers to raise a support ticket with Atlassian to restore app functionality when faced with such scenario.
The app reactivates correctly when no re-installation was attempted after suspension.
We are working on a plan to fix this issue.
We are continuing our investigation to understand if there is no recent change in system that could cause this scenario to be happening more frequently.
We will post next update in 24 hours - by the 2024-06-13 9:30 UTC.
Jun 12, 2024 - 09:50 UTC
Investigating - We are investigating an issue impacting paid apps after their license being suspended due to non-payment, and then reactivation fails even after making payment. We will provide more details once we identify the root cause.
Jun 12, 2024 - 06:45 UTC
Here we will post updates about Jira's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.
Resolved -
Between 03:23 UT to 07:09 UTC, we experienced intermittent page crashes for Jira. Users would have received a Something is wrong error when visiting board timelines. The issue has been resolved and the service is operating normally.
Jun 7, 07:17 UTC
Identified -
We continue to work on resolving the issue where Jira may respond with a 'Something went wrong' message when creating issues from Jira Software. We have identified the root cause and expect recovery shortly.
Jun 7, 06:04 UTC
Investigating -
We are investigating reports of intermittent errors for some Jira Cloud customers who are experiencing crashes when creating issues from Jira. We will provide more details once we identify the root cause.
Jun 7, 05:18 UTC
Resolved -
Between 22:18 UTC to 22:56 UTC, we experienced errors for multiple Cloud products. The issue has been resolved and the service is operating normally.
Jun 4, 00:35 UTC
Identified -
We are investigating an issue with error responses for some Cloud customers across multiple products. We have identified the root cause and expect recovery shortly.
Jun 3, 23:11 UTC
