The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
How AI can help your impact analysis in Jira?
Hello!
This is the round 2 of the Impact Analysis for Jira. To rewind a bit: Impact analysis is a custom solution that helps the users to know the consequences before any change has been made.
The problem: Jira doesn't alarm users when they are about to make a change: change a project key, deactivate a user, change the name of the status.
When impact happens, filters, dashboards, automation rules are broken.
Executives get frustrated, ops team is frustrated with automation rules not working, and you take the blame.
Not anymore.
With the new AI feature, Impact Analysis has its own Rovo agent that helps the users to understand the problem and score those problems based on the risk of the change. Not only that.
Custom fields (FOR NOW) got the upgrade as well. When you want to delete/edit the custom field an impact diagram is shown to you, where you can see what will happen after the change.
Think twice before the change.
https://marketplace.atlassian.com/apps/4251492671/impact-analysis-for-jira
Was this helpful?
Thanks!
Nikola Perisic
0 comments