Cappsule Outage History

Cappsule is up right now

Cappsule had 4 outages in the last 2 years totaling 916h 55m of downtime, averaging 0.2 incidents per month.

There were 4 Cappsule outages since December 19, 2024 totaling 916h 55m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: atlassianpluginsbycappsule.statuspage.io

Minor September 11, 2025

Jira API permissions is not working properly

Detected by Pingoru
Sep 11, 2025, 12:47 PM UTC
Resolved
Oct 17, 2025, 09:06 AM UTC
Duration
35d 20h
Affected: Chart Factory for JiraTimeFlow for JiraTimesheet tracking for JIRA
Timeline · 4 updates
  1. investigating Sep 11, 2025, 12:47 PM UTC

    We are currently investigating this issue and waiting for Atlassian feedback.

  2. investigating Sep 12, 2025, 12:35 PM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 17, 2025, 09:06 AM UTC

    This incident has been resolved.

  4. postmortem Oct 17, 2025, 09:06 AM UTC

    The issue is resolved. Sometimes, permissions needed to be fetched twice which is considered as an issue by our company. The impact on end users was completely transparent but we wanted to keep track of it until its resolution.

Read the full incident report →

Major June 10, 2025

Timesheet pages are not accessible intermittently

Detected by Pingoru
Jun 10, 2025, 02:30 PM UTC
Resolved
Jun 11, 2025, 03:33 PM UTC
Duration
1d 1h
Affected: Timesheet tracking for JIRA
Timeline · 2 updates
  1. investigating Jun 10, 2025, 02:30 PM UTC

    We are currently investigating this issue.

  2. resolved Jun 11, 2025, 03:33 PM UTC

    The incident has been resolved. The issue was caused by our hosting server that was experiencing problems and failed to process all requests. The impact was minimal and affected few users from two companies

Read the full incident report →

Major February 10, 2025

Malfunction in the API retrieving worklogs

Detected by Pingoru
Feb 10, 2025, 11:38 PM UTC
Resolved
Feb 12, 2025, 04:34 AM UTC
Duration
1d 4h
Affected: Timesheet tracking for JIRA
Timeline · 5 updates
  1. investigating Feb 10, 2025, 11:38 PM UTC

    We are noticing malfunctions with the API retrieving worklogs. Some worklogs may be duplicated or missing from the results. This impact only third party addons and not JIRA itself, so you may continue logging your time as usual. But calendars and reports may be inconsistent We are currently investigating this issue.

  2. investigating Feb 10, 2025, 11:38 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 11, 2025, 11:07 AM UTC

    The issue has been identified. The new Jira Search API returns a maximum of 20 worklogs, causing the Timesheet app to loop when this limit is exceeded. We discovered that the Jira API sometimes sends duplicate or missing entries due to how the data is sorted—once by the worklog's start date and once by its creation date. To resolve this, we are adding a processing step to collect all worklogs and ensure they are unique. We are testing the fix and will roll it out in the next few hours.

  4. monitoring Feb 11, 2025, 11:41 AM UTC

    The issue has been identified. The new Jira Search API returns a maximum of 20 worklogs, causing the Timesheet app to loop when this limit is exceeded, as explained yesterday during the meeting. We discovered that the Jira API sometimes sends duplicate or missing entries due to how the data is sorted—once by the worklog's start date and once by its creation date. So the first 20 worklogs are sent by JIRA by started date. Then the following 20 to 5000 are sent based on the creation date . So depending on this , we can have missing or duplicate entries. There is no reason that Jira sends two different orders like that. But we were able to implement a workaround to re-ask again Jira for all worklogs from 0 to 4999 and then 5000 - 9999. Instead of 0-19 then 20-4999 etc… We have already published the fix. Meanwhile, we are raising a ticket to Atlassian to get the explanation why the results are not ordred the same way. Best regards,

  5. resolved Feb 12, 2025, 04:34 AM UTC

    The incident has been resolved. We got the confirmation from end users that the results are now consistent

Read the full incident report →

Critical December 19, 2024

Timesheet pages are not accessible

Detected by Pingoru
Dec 19, 2024, 08:00 AM UTC
Resolved
Dec 19, 2024, 10:38 AM UTC
Duration
2h 38m
Affected: Timesheet tracking for JIRA
Timeline · 2 updates
  1. investigating Dec 19, 2024, 08:00 AM UTC

    We are currently investigating the issue . Some companies can not open the Timesheet pages. A workaround would be to first navigate to the desired module and then refresh the page. It seems to be an Atlassian general problem regarding the marketplace apps so we are connecting with Atlassian support teams to fix the issue

  2. resolved Dec 19, 2024, 10:38 AM UTC

    This incident has been resolved.

Read the full incident report →