Vendor Status Watch

← all vendors

Jira Work Management status history

Current state: operational — “All Systems Operational” per https://jira-work-management.status.atlassian.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
2incidents, last 90 days
19incidents on record
Incidents per week, last 12 weeks:

How long do Jira Work Management incidents last?

2.5 hmedian incident duration19 measured
21.5 h90th percentile1 in 10 ran longer
2.6 hmedian, major/critical only10 incidents

From 19 incidents with a vendor-posted start and resolve time. Longest on record: Degraded performance in Confluence and Jira for Microsoft Edge users — 5.8 days (2025-09-09 10:23 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (19)

StartedIncidentStatusImpactDuration
2026-09-01 09:12 UTCJira - Work Item transition failuresresolvedminor2 h 31 min
2026-08-07 01:26 UTCDegraded performance of JIRAresolvedminor19 min
2026-06-01 08:06 UTCFor Jira-software viewIssues and viewBoard are degradedpostmortemmajor5 h 17 min
2026-05-14 05:11 UTCUsers experiencing issues accessing multiple Atlassian productspostmortemcritical1 h 37 min
2026-05-08 01:31 UTCMultiple Atlassian services are experiencing issuespostmortemminor18 h 13 min
2026-05-06 03:18 UTCJira users unable to log time while on business boardresolvedmajor3 h 21 min
2026-05-02 00:55 UTCThe Work Item view experience of Jira is restoredpostmortemcritical1 h 52 min
2026-04-14 12:12 UTCDisrupted Rovo availability for Automation rulesresolvedcritical3 h 58 min
2026-04-13 07:29 UTCUsers experiencing issues with login across Atlassian productspostmortemminor2 h 47 min
2026-03-10 00:06 UTCAutomation events delayed for some customers in the APAC regionresolvedmajor52 min
2025-12-27 04:42 UTCOutbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Productspostmortemcritical37 min
2025-12-15 16:26 UTCDegraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovoresolvedminor2 h 35 min
2025-12-01 17:24 UTCDegraded Performance for Some Jira Usersresolvedminor1 h 02 min
2025-11-15 16:29 UTCSome users are unable to send emails from Jiraresolvedmajor43 h 20 min
2025-10-27 16:33 UTCJira Platform Incident - viewIssue and createIssue Service Disruptionresolvedmajor1 h 16 min
2025-10-20 07:56 UTCAtlassian Cloud Services impactedpostmortemmajor21 h 28 min
2025-10-15 13:43 UTCUnable to perform UI Operationsresolvedminor2 h 32 min
2025-09-22 05:38 UTCDegraded performance to multiple Atlassian experiencespostmortemminor1 h 38 min
2025-09-09 10:23 UTCDegraded performance in Confluence and Jira for Microsoft Edge usersresolvednone5 d 20 h

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Jira Work Management with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "jira-work-management"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}