No More Incident Communication Stress: Introducing Status Pages and AI-Powered Updates in JSM!

[#1]

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 customers) and AI features in Jira Service Management – powered by Rovo (including Smart Stakeholder Suggestions rolling out to both Premium and Enterprise plans and Auto drafting status page updates for Enterprise plans)!

Mark your calendars! These features are being gradually rolled out starting 16th February,2026 and should be available on all instances within a few weeks 🚀

What’s New?

1. Native Public Status Pages: You can now create and manage branded, real-time status pages directly within JSM—no separate app required^. Use these to communicate service health and incident updates to keep your customers informed and reduce support ticket volume.

Feature	Details
Custom Branding	Add your logo, colors, favicon, and even use a custom domain
Subscriber Management	Stakeholders can subscribe via email or webhooks for real-time alerts
Service Registry Integration	Tie status page components directly to your Jira Service Registry
Zero Additional AI Cost	These AI drafting features work seamlessly with existing workflows

2. AI-Powered Auto-Drafting (Open Beta): Speed up your communications with AI that drafts your status page titles and messages using incident data. It helps you get the word out faster without the manual effort.

3. Smart Stakeholder Suggestions (Open Beta): JSM now analyzes past similar incidents to proactively suggest stakeholders who should be added to the loop, ensuring no key person is missed during critical moments.

Watch it in action!

---

Admin & Agent Quick Start Guide

For JSM Administrators: Creating & Managing Status Pages

Jira Admins can now build a native communication hub without needing an external Statuspage subscription.

• Access the Entry Point: Navigate to Operations > Status pages within Jira Service Management to begin.

• Create Your Page: Select the page type (Public pages are currently available; Private pages are coming soon) and define a unique default URL.

• Configure Components: Link your status page components directly to the Jira Service Registry to display the health of specific services.

• Customize Branding: Tailor the appearance by adding your logo, colors, favicon, and a custom domain.

• Manage Subscribers: Set up notification channels via email or webhooks (which can be extended to Slack or MS Teams). Note: There is a limit of 10,000 subscribers per site.

Read more on how to create your first status page.

For JSM Agents: Sending Incident Updates

Agents can communicate with stakeholders directly from the incident record, keeping technical work and communications in a single view.

• Trigger Updates: Updates can be sent from any "system incident" work item type in ITSM templates or projects with the Incident Management category enabled.

• Leverage AI Drafting: Use the Auto-draft feature to let Atlassian Intelligence generate a suggested title and status message based on the incident data.

• Review and Post: Review the AI-suggested content, make any necessary manual tweaks, and publish directly to the status page.

• Identify Stakeholders: Use the Suggested Stakeholders tool, which uses AI to identify the right people to notify based on past similar incidents and send email communications.

Get started with your incident updates.

---

What’s next?- Private/Login gated Status pages

While we are excited to bring Public Status Pages to General Availability, we know that many of you need a secure way to communicate sensitive updates internally. We are officially opening the Early Access Program (EAP) for Private Status Pages in Jira service management!

• Audience-Specific Comms: Private pages will allow you to share service health and incident updates exclusively with internal teams or specific stakeholders.

• Secure Access: Ensure that sensitive incident details remain within your organization while still providing the same real-time transparency as our public pages.

Interested in being an early adopter? We are looking for Enterprise customers to test this functionality and provide feedback to help shape the final product. Fill out this form and we will keep you posted on the next steps!

---

We want to hear from you! How do you currently manage your incident communications? Are you excited to try out the new AI drafting? Share your thoughts or questions below! 👇

[Dirk Ronsmans]

Great, I feel that Statuspage is heavily underused as a tool within the Incident Mangement practice.

A bit bummed that it's limited to Enterprise though, Premium would have been great (and hopefully on the roadmap)!

[Dave Mathijs]

Hi @Deeksha While Statuspage is yet another app (= context switching), I'd like to see it integrated with the Announcement banner in the JSM Customer Portal. Is this being considered?

[Deeksha]

Completely agree with you @Dirk Rosemann on status pages being underused and unleashing the capability to manage broadcasting updates, enabling self serve and streamlining the process to communicate on incidents! 

I have created a feature request for extending it to premium licenses, so feel free to vote and add your use cases as it will help us evaluate the need!

[Deeksha]

Thanks @Dave Mathijs for calling out this capability. We do have it in our backlog, but I have also created a feature request that can be used to communicate more on this ask in the future!

[Martin Runge]

Thank you, @Deeksha, for those great updates! I would like to see the Status Pages in JSM in Premium plans as well.