JIRA

🟠 Jira's email-to-ticket pipeline forgot how to read Microsoft OAuth credentials, leaving some customers with a pile of unprocessed messages. Now fixed, but affected folks need to re-auth their mail servers like it's their first day on the internet again. (Auto-resolved: no updates in 24h)

⏰ Jun 19, 2026 Fixed (for now) spotted via status_rss

// The official story

Jira : Incoming emails partial outage

// Status page says

Jun 19 , 22:46 UTC Monitoring - Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server

🔗 Official status page (for the PR-approved version)

https://jira-software.status.atlassian.com/incidents/wz4nsfzcddyv

Jira's Greatest Hits

🟢 JIRA Sep 03, 2026

🟡 JIRA decided to ghost US East users mid-afternoon. Turns out distributed systems are like relationships: sometimes one side just stops responding and nobody knows why. Engineers are 'actively investigating' which is corporate for 'we're refreshing our dashboards every 30 seconds and stress-eating snacks.'. (Auto-resolved: no updates in 24h)

🟢 JIRA Sep 01, 2026

⚪ Your tickets spent 7 hours refusing to move between states like they had commitment issues. Atlassian found the root cause, applied the metaphorical duct tape, and declared victory. All your blocked sprints can finally unblock. (Auto-resolved: no updates in 24h)

🟢 JIRA Aug 27, 2026

⚪ Jira, Confluence, and Service Management took an unscheduled vacation across multiple regions, leaving teams staring at error pages. Atlassian flipped the switch back on and now pretends nothing happened. Postmortem coming soon, probably written in a very calming font. (Auto-resolved: no updates in 24h)

🟢 JIRA Jul 06, 2026

🟠 Atlassian's dynamic duo went full Sleeping Beauty for a bit—automation was napping hard. Fix deployed, recovery underway, though anything submitted during the blackout is now digitally deceased. Full resurrection expected within the hour if the universe cooperates. (Auto-resolved: no updates in 24h)