The ROAM report would be useful but it is limited and we are not able to use it as is to share during PI planning or in MBR, QBR or export to share:

1- UX - the titles are cut short and when there are many risks, our users expect the table to expand

2- All the data is in the database, why can we only see the data for one tribe and one quarter when we need to review risks by Portfolio (since risks can be associated with Themes and initiatives), Program and team level (no risks created at team level, but if there is a story associated with a feature/initiative/theme risk, we ought to be able to filter by team).

3- Can't filter by impact, critical path, occurrence and status. During reviews, we see a lot of information, help us identify quickly which risks need the most attention.
4- Risks should be visible in the Program board and the roadmap so they receive the attention they need where users spend the most time. The Program room is not enough.
5- It is often the case that the individuals who can provide support, resources, decisions to mitigate or remove a risk are not Jira Align users. Ideally, we could display the report in Confluence as read-only, as we do with Advance Roadmap, or we could export the ROAM report (with the updated UX) to include it in a slide, a reporting tool (pdf, image), so external individuals can take action. 

Feasibility:

It seems like the effort to make this report very valuable with great UX is small and would be useful to all Jira Align customers. The additional information to display must be in the database already.

Impact of a poor experience with risks:

• Risks often require additional support to the teams, but if we are not able to see what help is needed, we discover issues late and this impacts our throughput. Risks are best dealt with early, help us with more visibility to the risks, better filtering so we can tell who needs to provide support and better UX we can easily use as is in our review meetings.
• Replacing manual reporting is part of the ROI of Jira Align, and currently, we are not able to abandon our existing manual reporting process.