Hello Atlassian Community! We’re excited to share a few new updates to streamline change review and approval: new risk insights parameters, and new customization options for risk insights.
Before, when an approver was evaluating a change request, they could see details like conflicting changes, freeze windows, and ongoing incidents on affected services.
Now, we’re surfacing more risk insights on change requests: success rates for previous changes and previous deployments. These new insights help give approvers more context on each change request, making it easier to make informed decisions, faster, and keep the flow of work moving across dev and ops.
Get a quick look at what’s new in this 4-minute demo, or read on for details:
With this launch, we’re introducing 3 new risk insights parameters to give your change advisory board more context on incoming changes:
Success rate of all changes on affected services: The number of change requests that have been approved by the change advisory board on relevant services within the last 30, 60, or 90 days
Success rate of deployments on the affected services: The number of deployments that have failed on the services that this change will impact, looking back at changes in the last 30, 60, or 90 days
Success rate of previous changes from the issue reporter requesting a change: How many of the changes submitted by this issue reporter have been approved vs. declined by the change advisory board in the last 30, 60, or 90 days
By collecting these new insights directly on the change request, approvers can spend less time digging for context, enabling them to act on change requests faster while keeping risk in check.
With these added parameters, they can quickly zero in on how similar changes have unfolded (like change success rate on the affected service), helping them approve more confidently where they see similar changes have introduced minimal risk.
And on the flip side, when there is a recent history of failed changes, change approvers can also drill down into those failed changes for more information on where they went wrong:
As a part of this launch, we’re also releasing new customization options for risk insights. Now, you can pick and choose which risk parameters to show on a change request, and which to hide from approvers:
With these new customization options, you can tailor your risk insights to suit the unique needs of your team:
Toggle which risk insights parameters do—and don’t—show up on a change request: Hide or show any parameter from changes in your project, including changes, incidents, maintenance or freeze windows, or any of the new parameters covered above
Customize your definition of a “rejected” change: Choose which issue status (or statuses) should count as a rejected change
Determine how far back to look for rejected changes or failed deployments: Pick a lookback period of 30, 60, or 90 days to assess changes from
By picking and choosing the parameters best aligned to your team’s approval process, you can customize your change approvers' experience. This helps change them zero in on the parameters most important to you, and de-emphasize the ones that aren’t critical path, so you know your changes are being held to a consistent standard.
Note: By default, the risk insights you see on your changes will remain as-is. Admins will need to update preferences in change management settings to configure the new risk insights, and toggle them on.
Let us know what you think! We’d love to hear any thoughts, questions, or feedback you have on these new releases. Feel free to drop any questions or suggestions here, or submit it via our feedback portal.
Prithwish Basu
4 comments