SoftwarePlant incident

Disabled Jira webhook synchronisation

Major Resolved View vendor source →

SoftwarePlant experienced a major incident on May 4, 2026 affecting BigPicture Jira Cloud App, lasting 7d 17h. The incident has been resolved; the full update timeline is below.

Started
May 04, 2026, 01:18 PM UTC
Resolved
May 12, 2026, 06:34 AM UTC
Duration
7d 17h
Detected by Pingoru
May 04, 2026, 01:18 PM UTC

Affected components

BigPicture Jira Cloud App

Update timeline

  1. identified May 04, 2026, 01:18 PM UTC

    We are currently experiencing issues with webhooks (Jira events), which may result in a lack of data synchronization between Jira and BigPicture. Our team is actively working on resolving the problem. We will provide an update as soon as more information becomes available.

  2. identified May 04, 2026, 01:20 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified May 05, 2026, 10:55 AM UTC

    Some Jira issues may not sync with BigPicture due to non-working webhooks. Workarounds: • Task data issues → use Resynchronize from the menu • Other issues → Clear cache ETA: 08 May (8.05)

  4. identified May 08, 2026, 12:21 PM UTC

    Some Jira issues may not sync with BigPicture due to non-working webhooks. Workarounds: • Task data issues → use Resynchronize from the menu • Other issues → Clear cache ETA: 12 May (12.05)

  5. monitoring May 08, 2026, 02:40 PM UTC

    We’re receiving 40% of webhooks and monitoring the rollout with Atlassian before moving to 100%.

  6. monitoring May 11, 2026, 06:23 AM UTC

    We’re receiving 70% of webhooks and monitoring the rollout with Atlassian before moving to 100%.

  7. monitoring May 11, 2026, 10:25 AM UTC

    We’re receiving 80% of webhooks and monitoring the rollout with Atlassian before moving to 100%.

  8. monitoring May 11, 2026, 11:14 AM UTC

    We’re receiving 90% of webhooks and will gradually increment this further till 100%

  9. monitoring May 11, 2026, 01:19 PM UTC

    We are now receiving all webhooks. We’re continuing to monitor the system closely to ensure everything is working as expected.

  10. resolved May 12, 2026, 06:34 AM UTC

    This incident has been resolved.