FastRisk app icon

Nirama Solutions

FastRisk — Risk Matrix & RAID Log for Jira

The risk matrix your steering meeting wants

Every project tracks its risks in a spreadsheet nobody opens between steering meetings. FastRisk makes risks ordinary Jira issues: assess any issue on tap-friendly 1–5 scales and it appears on the matrix. No import, no sync, no shadow database.

The FastRisk 5x5 risk matrix inside Jira: band totals for low, moderate, high and critical across the top, and issue keys placed in coloured cells by likelihood and impact
A 5×5 matrix with the critical corner top-right. Each cell shows the risks inside it; drag one to another cell and it is re-assessed.
Why it is different

Risks are Jira issues, not rows in a second database

The assessment lives in real Jira custom fields on your own issues. That is not an implementation detail — it is the whole point.

Queryable in JQL

"Risk score" >= 15 works in Jira's own search, in a saved filter, on a board, and in any dashboard you already have.

Six fields, and only six

Likelihood, impact, score, RAID type, mitigation and review date. The platform restricts FastRisk to the fields it owns, so no summary, status, assignee or other app's field is reachable — by construction.

No personal data at all

Not a name, not an email address, not even an Atlassian account ID. Risk owners are read from Jira when a page is rendered and never written to app storage.

In the product

From the matrix to the meeting

A RAID log, not just risks

Risks, Assumptions, Issues and Dependencies in one register, grouped by type, sortable on every column, searchable across key, summary, owner and mitigation. An untyped item reads as a Risk, so a team that only wants a risk register never has to learn the taxonomy.

Each risk carries a sparkline of its score over time, so “this one is getting worse” is visible without reading numbers.

The FastRisk RAID register grouped by type, with columns for key, summary, score band, owner, status, mitigation and review date
The register, grouped by RAID type. Overdue review dates are called out in red.

Open a cell, see what is in it

Click any cell for the risks inside: key, summary, owner, status, mitigation, review date, and a click through to the issue. Re-assess from the drawer — the accessible route to the same change that dragging makes.

A FastRisk matrix cell opened as a drawer, listing the risks in that cell with owner, status, mitigation and review date
Two fields written, nothing else touched — and Jira's own issue history records the change.

Assess without leaving the issue

The assessment panel sits on the issue and needs no screen configuration at all. Likelihood and impact on 1–5 scales, the score and band computed as you pick.

The FastRisk assessment panel on a Jira issue, with likelihood and impact scales and the resulting risk score and band
Every read runs as the signed-in user, so FastRisk cannot surface an issue somebody could not already find in Jira.

The portfolio view

A dashboard gadget spanning any JQL you like — several projects, a programme, the whole site — showing how much sits in each band and the top risks worst-first. Each viewer sees only the issues they could already find in Jira's own search.

The FastRisk dashboard gadget showing band totals and the highest-scoring risks across a JQL scope
Export the matrix as a PNG and the register as a CSV — both generated in your browser, both showing exactly what is on screen.
Stated plainly

What FastRisk does not claim

We would rather you find this here than after you install.

It is not a compliance tool

No control libraries, no audit trails against a framework, no evidence workflows, no attestations. If your organisation needs validated compliance processes, FastRisk is not that product.

Fields are invisible on the issue view until an admin adds them to screens

They are queryable in JQL immediately and the assessment panel needs no screen setup at all — so this costs inline visibility, not function.

Band names on native Jira surfaces are the app defaults

A project that retunes its thresholds sees its own wording inside FastRisk and the defaults in Jira's list view, issue navigator and notification emails. A field formatter is a static expression and cannot read per-project configuration.

Drag re-assessment is pointer-only

Drag-and-drop cannot be driven from a keyboard. The cell drawer's Re-assess opens the same editor and is the accessible route to the same change.

Before you choose

How FastRisk compares to the alternatives

At 100 users the paid risk apps run from $20 to $400 a month for the same 5×5 grid. The comparison page has the whole table, the architectural fork between “risks are Jira issues” and a separate register, and a section on what Risk Register, Hedge and SoftComply each do better than we do.

Get FastRisk for your Jira site

Install it from the Atlassian Marketplace, which carries the current pricing and tiers. The guide here covers every feature, every limit and the troubleshooting section.