Riskcadence for JiraJira Cloud · Built on Forge · Confluence optional

The risk register that lives in Jira

Every risk is a Jira work item. A configurable risk matrix, a review inbox, review sessions with an audit trail and a steering report for your committee, in Jira and Confluence. The heat map and the review inbox also run on Jira dashboards.

Free for Jira sites with up to 10 users. Larger sites start with a free trial.

In your Jira

What you get

Screenshots from a real Jira site with sample data.

The Riskcadence register in Jira: risks grouped by level with likelihood, impact, score, residual score, owner, response, mitigation progress and next review, editable in place. Inset: the heat map of the open risks by likelihood and impact

A risk register in Jira

Every risk is a Jira work item of the type Risk. The register lists them with score, level, owner, response, mitigation progress and next review, and you change most of it in place.

  • Search, filters, grouping and columns; save a view and share it with your team.
  • Bulk edit, and export of the current view as CSV or XLSX.
  • A heat map shows where the open risks sit; click a cell to see its risks.
More in the docs →
Video

Watch the tour

A short walkthrough of Riskcadence in Jira.

Why the app

Jira alone vs. with Riskcadence

Jira aloneWith Riskcadence
Assessing a riskCustom fields that you create and keep consistent by handLikelihood and impact on your own matrix, with score and level calculated for you
Knowing what to reviewA saved filter that you build and check yourselfA review inbox: overdue, due in 7 days, without an owner, needs re-assessment
Recording a decisionThe work item history shows field changes, not who accepted a risk and whyReview sessions keep each decision with the person, the date and the justification
Reporting to a committeeCounts on a dashboard, or a spreadsheet that someone updates by handA steering report with heat map, top risks and changes since the last review

Compared with Jira Cloud and Confluence Cloud without apps.

Plans

Free for small sites, per user above

Free for up to 10 users

No cost on Jira sites with up to 10 users, with every feature.

  • Risk register, matrix, issue panel and import
  • Review inbox, sessions and comparison
  • Steering report in Jira and in Confluence
  • Dashboard matrix and review inbox

11 users and more

Larger sites start with a free trial; after the trial it is priced per user, with graduated prices per user and month in USD:

  • 11–100 users: 0.79
  • 101–250 users: 0.59
  • 251–1,000 users: 0.39
  • 1,001–2,500 users: 0.29

Billing and the trial are handled by Atlassian through the Marketplace.

Setup

Running in three steps

1

Install

Once the app is live on the Atlassian Marketplace, a Jira admin installs it on the Jira site.

2

Set up a project

Open Riskcadence in a project and click Set up project. In company-managed projects a Jira admin does it in one click; in team-managed projects a project admin follows a short checklist.

3

Add risks

Add risks in the register, import a spreadsheet or add six example risks. Then open the review inbox and the steering report.

FAQ

Common questions

More answers in the documentation, or write to support@janekbehrens.de.

How do I set up a risk register in Jira?
Open Riskcadence in your project, choose a risk matrix template and click Set up project. In company-managed projects a Jira admin does this in one click: the app adds the work type Risk, seven fields, a link type for mitigations and the screen entries. In team-managed projects a project admin adds the work type and the fields by hand, following a checklist, and Riskcadence checks them. Six example risks are optional.
Can I use my own risk matrix?
Yes. Start from a 5×5, 4×4 or 3×3 template, rename the steps, change the colours and set the level of every cell. Each level has a review interval. Saving creates a new version of the matrix, and earlier reviews keep the version they were made with.
Does it work in team-managed projects?
Yes. A project admin adds the work type Risk and the seven fields once, following a checklist in Riskcadence. Jira does not show app-calculated fields in team-managed projects, so Risk score and Risk level are missing from the work item there; Riskcadence still shows score and level in the register, the panel and the reports.
How do reviews work?
The review inbox lists risks that are overdue, due within seven days, without an owner, or that need a re-assessment because all mitigations are done. In a review session your team confirms, re-assesses, accepts or closes each risk. Accepting a risk needs a named person, a date and a justification of at least 10 characters. Closing the session freezes the state as a baseline for the next comparison and report.
Can people without Jira access read the steering report?
Yes, in Confluence. A page editor publishes the current state of the report on the page with one click, and everyone who can view the page sees it with its date, also without Jira access. The editor can withdraw it at any time. A live report shows every reader what their own Jira permissions allow.
Can I see how risks changed over time?
Yes. The steering report of a project shows the risk trend across reviews: the open risks per risk level at each of the last six closed reviews and now, as stacked bars. Each closed review adds a bar. Reports across several projects do not show the trend.
Does any data leave Atlassian?
No. The app runs on Atlassian Forge with no external servers, no external services and no AI. It reads and changes risks with each person's own Jira permissions. Review sessions, history and published reports are kept in Atlassian's Forge storage.
Is it free?
Jira sites with up to 10 users pay nothing, with every feature. Larger sites start with a free trial; after the trial it is priced per user, from USD 0.79 per user per month.

Your risk register, reviews and reports in one place

Free for Jira sites with up to 10 users. Larger sites start with a free trial.