Cappsule incident

Outage in Timesheet tracking for JIRA

Critical Resolved View vendor source →

Cappsule experienced a critical incident on February 28, 2024 affecting Timesheet tracking for JIRA, lasting 3h 46m. The incident has been resolved; the full update timeline is below.

Started
Feb 28, 2024, 01:43 PM UTC
Resolved
Feb 28, 2024, 05:29 PM UTC
Duration
3h 46m
Detected by Pingoru
Feb 28, 2024, 01:43 PM UTC

Affected components

Timesheet tracking for JIRA

Update timeline

  1. investigating Feb 28, 2024, 01:43 PM UTC

    Currently, a number of Atlassian Marketplace plugins are experiencing access problems. We are working closely with the Atlassian team to address this issue and will provide updates as soon as possible.Currently, it appears that the JIRA REST API endpoint concerning users is not responding effectively to requests.

  2. investigating Feb 28, 2024, 02:05 PM UTC

    https://developer.status.atlassian.com/ Investigating - We have identified a problem with Connect apps where user impersonation is not working properly. We are investigating the root cause and will provide another update by 14:30 UTC.

  3. monitoring Feb 28, 2024, 04:51 PM UTC

    Atlassian is implemeting a fix and they are monitoring the status over all services and affected plugins,.

  4. monitoring Feb 28, 2024, 04:53 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 28, 2024, 05:29 PM UTC

    Resolved - On 28th Feb between 12:15 UTC and 15:20 UTC Connect apps were unable to perform user impersonation operations. Atlassian have identified fault and resolved it by scaling up the infrastructure. The incident is now resolved. Atlassian will now engage in post incident review and detailed root cause investigation, which will be shared in form of public PIR.

  6. postmortem Feb 28, 2024, 05:29 PM UTC

    On 28th Feb between 12:15 UTC and 15:20 UTC Connect apps were unable to perform user impersonation operations. Atlassian have identified fault and resolved it by scaling up the infrastructure. The incident is now resolved. Atlassian will now engage in post incident review and detailed root cause investigation, which will be shared in form of public PIR.