Deeksha Atlassian Team

👋 Hi Community, We've been listening — and we know that not every status update is meant for the world. Sometimes you need to keep your customers, employees, or partners in the loop without publishing to a public page. Today, we're excited to announce Private Status Pages in Jira Service Management Enterprise are GA. 🎉…

Hi everyone 👋 It's been a busy quarter for Status Pages in Jira Service Management. We've shipped three new capabilities that customers have been asking for - each one aimed at a specific moment of pain in the status-page lifecycle. Here's what's new and how to use it. 1. "Send update to Statuspage" is now a Jira…

Hi Community! During an incident, your priority is fixing the problem—not spending precious minutes drafting the perfect update or hunting for the right stakeholders. We’re excited to announce that we are bringing communication directly into your workflow with native Public Status Pages (available for Enterprise plan…

👋 Hi Community, If you've ever had an alert close itself just as the underlying issue came roaring back — or hit "close" a second too early and lost all the context — we have good news. From June 18, 2026, you can reopen a closed alert in Jira Service Management- Operations without losing any of its history, links,…

To enhance security and better protect our customers from potential vulnerabilities, we’re making changes to how Statuspage API keys work. These changes are being introduced to ensure the security of API tokens used to access Statuspage. We also sent email communications about these changes to Statuspage admins in January…

Keeping stakeholders informed during an incident is crucial and increasingly complex. As service teams grow, incidents can affect a broad range of stakeholders, including internal teams, external partners, customers, and leadership. Unfortunately, relying on manual email updates, ad-hoc distribution lists, and disconnected…