Guide · Jira Cloud
Track project risks on a 5×5 heat map
Spreadsheets drift the day after you export them. Project leads need a living risk register next to the Jira work — score probability × impact, set a response, and see the portfolio heat map in one place.
30-day try-it-free · Free ≤10 users · then USD 1.50/user/mo
01 — The gap
Why spreadsheet risk logs fail in Jira teams
Risk owners change, scores go stale, and the file lives outside Jira. By the time a portfolio review happens, nobody trusts the sheet. Teams need the register on the project page, with an audit trail and a combined heat map for the projects they can see.
02 — What buyers usually want
Score, respond, import, review
- Add risks on the project with probability and impact (1–5) so score = probability × impact.
- Choose a response — avoid, mitigate, transfer, or accept — plus mitigation notes and a next-review date.
- Import CSV with a dry-run so existing lists do not get retyped by hand.
- Portfolio heat map across projects you can access; filter by category, band, and status.
- Re-score visually by dragging a risk onto a matrix cell when priorities shift.
03 — Tooling
Risk Register for Jira
Risk Register for Jira is a Forge app: project register, issue panel, and portfolio heat map on Jira Cloud. Risk records stay in Atlassian Forge storage on your site — no customer risk data leaves Atlassian.
Marketplace listing: Risk Register for Jira. Support: info@berkly.nl.