Blog ·

Jira risk register: set one up, score it, and keep the reviews coming

A Jira risk register is a set of Risk issues in one project, each with a likelihood, an impact, an owner and a next review date, plus a saved filter that ranks them. A default Jira software project has no risk register, but everything a register needs is ordinary Jira: an issue type, a few custom fields, a workflow and JQL. The part most registers lose is the review. Teams fill the list in at kickoff, nobody opens it again, and the register quietly describes a project that no longer exists. This guide sets the register up and then makes the review happen on a schedule.

Statements about Jira's built-in features are as of October 2026, from Atlassian's own documentation.

What a risk register in Jira needs #

A spreadsheet register works until two people edit it, or until someone asks who agreed to accept a risk last spring. Jira answers both, because every risk is an issue with a history, an assignee and comments.

Register column Where it lives in Jira Notes
Risk title Summary Write it as a cause and effect: "Vendor API change breaks checkout"
Description Description What could happen, what would trigger it, what it would cost
Owner Assignee One person who watches it, even when others act on it
Likelihood Custom select field, 1 to 5 Agree what each number means before scoring
Impact Custom select field, 1 to 5 Same scale for every project, or scores cannot be compared
Score Custom number field Likelihood times impact, set by the reviewer or a rule
Response Custom select field Avoid, reduce, transfer, accept
Mitigation Linked tasks Real work items, so the action shows on a board
Next review Due date The date this risk must be looked at again
Status Workflow Open, mitigating, accepted, closed

The due date is the column that keeps the register alive. A risk with no next review date is a risk nobody will read again.

Set up the Risk issue type and fields #

You need project admin rights, and for custom fields a Jira admin, depending on how your site is set up.

  1. Create a Risk issue type in the project's issue types. A separate type keeps risks out of sprint boards and makes the filter simple.
  2. Add the fields: Likelihood and Impact as single select lists with the values 1 to 5, Score as a number field, Response as a single select list. Put them on the Risk issue type's screen only.
  3. Write the scale down. In the project's description or a pinned page, define each number. For example, likelihood 5 means "expected this quarter" and impact 5 means "stops a release or breaches a contract". Without a written scale, two reviewers score the same risk 6 and 20.
  4. Give it a short workflow: Open, Mitigating, Accepted, Closed. Accepted needs a comment saying who accepted it and why, which you can enforce with a validator on that transition if your plan allows it.
  5. Label or component the risks by area (security, delivery, vendor, people) so the register can be cut by owner team.

Keep the register in the project the work happens in when one team owns it. A shared risk project is better when risks span several teams and someone, such as a PMO, reviews them all together.

Score the risks consistently #

Scoring is where registers drift. Three habits keep it honest:

A 5 by 5 grid gives scores from 1 to 25. A common reading:

Score Band What happens
15 to 25 High Reviewed every month, mitigation task required
8 to 14 Medium Reviewed every quarter
1 to 7 Low Reviewed twice a year, or accepted

The bands are a choice for your team. What matters is that the band sets the next review date, so high risks come back sooner.

Mitigations as linked work #

A mitigation written into a text field never gets done, because nothing on any board shows it. Make each mitigation a task, story or bug in the team's normal backlog and link it to the risk with a link such as "is mitigated by". Then the risk shows its open actions, and the team sees the work where it already looks.

When the last mitigation task closes, the reviewer rescores the risk. Often the likelihood drops and the risk moves to a lower band, or it is closed.

The filters that turn issues into a register #

Three saved filters do most of the work. Replace PRJ with your project key.

  1. The register itself, ranked. project = PRJ AND issuetype = Risk AND statusCategory != Done ORDER BY Score DESC
  2. Risks overdue for review. project = PRJ AND issuetype = Risk AND statusCategory != Done AND due < now() ORDER BY due ASC
  3. Accepted risks, for the audit trail. project = PRJ AND issuetype = Risk AND status = Accepted ORDER BY updated DESC

Put the first filter on a dashboard as a filter results gadget showing Summary, Assignee, Likelihood, Impact, Score and Due. That is the register view people expect from a spreadsheet. A two-dimensional filter statistics gadget with Likelihood against Impact gives you a rough heat map without any app.

Subscribe the risk owners to the second filter weekly, so an overdue review lands in an inbox instead of waiting for the next meeting.

Make the risk review happen every month #

Here is the gap. The filters show which risks are overdue, but only if somebody opens them, and the monthly review meeting only happens if somebody books it and prepares it. The fix is a recurring Risk review ticket: one issue per cycle, assigned to the register's owner, due on the review day, with the checklist in its description.

A good review ticket description:

  1. Open the overdue filter and review each risk in it.
  2. Rescore any risk whose likelihood or impact changed, with a comment.
  3. Check the mitigation tasks linked to every high risk.
  4. Add new risks raised since the last review.
  5. Set each reviewed risk's due date to its next review, by band.
  6. Close the ticket with a one-line summary of what changed.

The resolved review tickets become the record that reviews took place. A filter of them, ordered by resolved date, answers "did you review your risks every month this year?" in one screen.

There are three ways to have that ticket appear.

Clone by hand Jira Automation scheduled rule A scheduling app
Who creates the ticket A person, every cycle A rule A rule in the project
"First Monday of the month" Whoever remembers Needs a cron expression Chosen in the form
Review day falls on a holiday Whoever notices Up to the rule's logic Set once for the project
Cost Time Counts toward your plan's automation usage App licence

Clone by hand #

Keep last month's review ticket and clone it. This is free and works while one dependable person owns the register. It fails in the month that person is away, and a missed risk review rarely announces itself.

Jira Automation #

Jira Automation's Scheduled trigger can create the review ticket on a timer. Atlassian's trigger reference says you can "run the flow at a fixed rate (for example, every 7 days), or use a Cron expression for more complex schedules." A review on the first Monday of each month is the complex kind; see our Jira cron expression guide for the syntax. Each run counts toward your plan's automation usage, explained in Jira Automation pricing. The same Atlassian page also notes:

Scheduled flows that reach a Failure status for 10 consecutive executions will disable automatically.

On a monthly rule, ten failures is most of a year without reviews.

A scheduling app #

Recurring Work Items for Jira is our app, and a monthly review is the kind of routine it was built for:

  1. Turn the app on for the project and choose who may schedule.
  2. Set the working week and add public holidays, so a review that lands on a day off moves instead of appearing when nobody is in.
  3. Create a rule that runs on a weekday position, such as the first Monday of the month.
  4. Title it with tokens so each review is named for its month, for example Risk review {{now.monthName}} {{now.year}}.
  5. Set the assignee, the checklist description and a due date as an offset from the run.

It uses no Jira Automation quota, because the scheduling is the app's own. Each created or failed run is written to the rule's history with its reason. A rule only creates tickets in the project it lives in. It is free for up to 10 users.

For a quarterly deep review of medium risks, add a second rule on a longer interval. The monthly one stays short.

Keep it light enough to last #

A register that takes an afternoon to update will be abandoned. A few limits help:

The Jira hygiene guide covers the same idea for the rest of a project: small, regular checks beat a big cleanup.

When the manual way is enough #

If the project is short, the team is small and one person runs the register, a spreadsheet linked from the project and a calendar reminder are enough. Move it into Jira when risks need owners on different teams, when mitigations should show up as real work, or when somebody will ask you to prove the reviews happened. Add the recurring review ticket when the meeting has been skipped once, because that is usually the first sign the register is going stale.

For other routines that suit the same pattern, see Jira change management template and Jira for project managers.

Frequently asked questions #

Does Jira have a risk register template? A default Jira software project has no Risk issue type, so you build the register from a Risk issue type, custom fields for likelihood and impact, and saved filters, as shown above.

How do I calculate a risk score in Jira? Either the reviewer enters the score when rescoring, or a Jira Automation rule sets the Score field to likelihood times impact whenever either changes. Both work; the rule removes arithmetic mistakes but counts toward your automation usage.

How often should risks be reviewed? Set it by band: high risks monthly, medium quarterly, low twice a year. Put the next review date in the due date so the overdue filter can find it.

Can I create a risk review ticket every month automatically? Yes. Use a Jira Automation scheduled rule, or create a monthly rule in Recurring Work Items for Jira with the review checklist in the description.