Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Creating Risk and Issue Register in Jira next generation

Hi,  I'm an admin for my project and need to create a risk and issue register for my project.  Can you please provide me with the steps how to create the register for ISSUE and RISK?


1 answer

1 accepted

0 votes
Answer accepted
Jack Community Leader Dec 08, 2020

Hi Allen, I’m not sure what you are referring to here - “issue and risk”. Can you educate me? Is there some reference to this within Atlassian docs?

It is important to clearly capture the key components to a risk.

  1. Title – a good description of the risk.
  2. Risk Detail – specific explanation of the risk.
  3. Risk Consequence – what will happen if the risk is not addressed.
  4. Target Resolution Date – the date by when the risk must be addressed or accepted.

Creat an issue log that helps managers track the issues that arise in a project and prioritize a response to them. ... An issue is something that has already come up in your project, and you need to identify and track that issue immediately.


I need to track and report issues and risks separately for my project.

Jack Community Leader Dec 08, 2020

ah ok got it!

So I would probably simply create a unique Issuetype for this called Risk. This would allow you to have a unique workflow and you can create the necessary custom fields to meet your needs.


  1. Title - this should be summary
  2. Risk detail - this could be the description (my recommendation) or you could create a completely new multi-line text custom field call Risk Detail
  3. Risk Consequence - i would create a new custom field for this
  4. Target Resolution Date - you could simply use the Due date (my recommendation but if you want create a new custom date field

you can then use workflow conditions/validators, etc to control when these fields/updates are required.

If this isn't helping, if there are more specific requirements here that I am missing please share.


Suggest an answer

Log in or Sign up to answer
Site Admin

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you