Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Creating Team Risks in Jira Align

Jira Align provides the ability to add risks to a program. As part of PI Planning as defined by SAFe ( ) teams may identify program-level risks. By adding a custom field for TEAMS on the RISK object, you have the ability to track the program risks by the team that raised the risk as part of PI Planning.


Screen Shot 2019-12-31 at 11.14.51 AM.png
Screen Shot 2019-12-31 at 11.16.58 AM.png

Add a field “Team for Risk” or something equivalent as a single selection drop down field and configure the page detail for Risk to show this new field.  Note that this field will be visible for the whole Jira Align instance and depending on the number of teams in your organization, it may get rather large.  


Screen Shot 2019-12-31 at 11.16.22 AM.png

Add the “Team for Risk” field on the RISKS list page. You can also apply a “Team for Risk” filter if you want to only see Risks for a specific team.


Screen Shot 2019-12-31 at 11.17.57 AM.png

It’s also suggested to add in parenthesis () the team name in the title since the RISK/ROAM report does not have the ability to filter or add the Team field to this view.  This could be another option instead of creating a custom field. 


Sam Tsubota Atlassian Team Jan 10, 2020

Great article on explaining how to create risks and viewing the Risk ROAM Report which is necessary for PI Planning especially when planning with remote teams. I wish I knew about the Risk ROAM Report in my past life as a RTE!

Like Tim Keyes likes this
DPK J Community Leader Jan 12, 2020

@Tom O_ConnorNicely explained.

I build a risk management platform back in 2010-11, but I was not aware of terms. If you have more helpful terms/links/articles to understand Risk space better, do hook me.

Tom O_Connor Atlassian Team Jan 16, 2020

@DPK J . ROAM stands for Resolved, Owned, Accepted, Mitigated and SAFe as part of PI Planning does define how to capture and track risks.

Like DPK J likes this
DPK J Community Leader Jan 16, 2020

@Tom O_Connor  Thanks, I will dig into all this stuff.


Log in or Sign up to comment

Atlassian Community Events