Hi Atlassian Community 
Preventing change-induced outages just got easier with two major updates in Jira Service Management: Prevention Center, a human-in-the-loop workspace for assessing change risk and planning mitigations, is now in Open Beta, and AI Change Risk Assessment has expanded with new risk categories.
By unifying full change context with actionable guidance, Prevention Center helps teams stop incidents before they start. Meanwhile, AI Change Risk Assessment now evaluates Business and Security & Compliance risk alongside technical factors, ensuring every change accounts for customer impact, financial exposure, and governance requirements based on your organization’s knowledge base.
Follow these steps to access the new features:
- In Jira Service Management, open Space settings for your change management space.
- Under Operations, select Change management.
- On the Risk assessment tab, locate Prevention Center and select Get started to begin setup.
- To configure additional risk categories, select AI risk assessment with Rovo on the same tab. Use the enable and configure guide for step-by-step guidance.
- Return to your change management space and open a change to review its summary, risk signals, and recommended mitigations in Prevention Center.
Read on to explore what’s new!
Prevention Center
Prevention Center in Jira Service Management delivers an AI-native, human-in-the-loop experience designed to help teams evaluate critical software and infrastructure changes before deployment. It empowers change managers and approvers to quickly understand what is changing, gauge potential blast radius, and apply mitigations before sign-off.
Critical change decisions often fail due to disconnected context across pull requests, past incident postmortems, and knowledge bases. Prevention Center unifies this operational context directly within Jira Service Management, cutting out manual investigation and helping teams balance deployment velocity with service stability.
Here is a closer look at the core capabilities available in Open Beta:
- Understand change context & trajectory: Rovo generates clear summaries of the present and target states, tracks progress across handoffs, and surfaces key change details alongside linked PRs and Jira issues. View an initial pre-risk indicator to see if a full assessment is needed, inspect the service dependency graph, and identify scheduling conflicts with other active changes.
- Assess risk across four dimensions: Evaluate Technical, Operational, Business, and Security & Compliance risks backed by cited evidence. Alongside deployment tracking and project KBs, AI risk assessment now supports direct PR links (GitHub, GitLab, Bitbucket) and Google Drive/Doc links in change descriptions or comments.
- Mitigate risks with human-in-the-loop control: Review tailored mitigation suggestions and generate draft plans (such as test, implementation, or rollback drafts) for manual review and execution, with no automatic actions taken without approver sign-off.
Note: Prevention Center (Open Beta) will be available in Service Collection Premium and Enterprise plans, and will be fully rolled out by the end of October 2026.
New risk categories for AI change risk assessment
Now available in the Prevention Center experience, AI change risk assessment reviews your change requests and surfaces risk scores, plain-language summaries, and suggested mitigation steps right inside Jira Service Management. To broaden the scope of AI change risk assessment, we’re adding two additional risk categories:
Business Risk
Technical reviews are important, but they don't always catch what a change could mean for the business. Business Risk can help fill that gap by surfacing financial and reputational factors based on your organization’s inputs and standards that deserve attention before a change goes through.
With business risk, change approvers get access to the following context:
- Financial exposure: estimated revenue impact, potential cost of downtime, or projected SLA penalties tied to affected services
- Reputational risk: changes that touch customer-facing systems or high-visibility services where disruption could affect customer trust
- Stakeholder impact: service owners, business stakeholders, and others who need to know about a potential disruption
Security & Compliance Risk
Security & Compliance Risk includes controls designed to help teams review change requests against your organization's connected security protocols, privacy guidelines, and industry standards, helping teams identify potential alignment issues before they reach production.
It helps identify:
- Security protocol gaps: whether the change is designed to support alignment with your organization's security standards and accepted industry practices
- Privacy concerns: potential privacy considerations that may require review under your organization’s data privacy knowledge base (e.g., GDPR or CCPA), attached to the project or change ticket
- Missing approvals: required sign-offs referenced in your knowledge base, linked tickets, or change description that haven't been obtained yet
As you begin trying out the new capabilities in Service Collection, feel free to share your feedback in the comments section below. If you run into any issues visit the support documentation for more details. Lastly, sign up for Prevention Center updates and future open beta programs.
We'll be watching this thread closely and using your input to shape what we build next for incident prevention in Jira Service Management.
Thanks for being part of the community!
