Frequently Asked Questions

Q. What data get stored on your servers?

A. Please refer to our Data Security and Privacy Statement.

Q. Can I add my own custom fields to the screens that are used for editing risks?

A. Yes. Adding your own custom fields to the Risk View screen or the Risk Edit screen is perfectly fine. The operation of the Risk Register add-on will not be adversely affected.

Q. Can I change the risk workflow?

A. Yes. The Risk Register add-on is generally tolerant of changes that you might make to the risk workflow. If you remove statuses from the original workflow configuration, or remove transitions between those statuses, then some of the add-on's automatic workflow progression will be disabled, but in other respects everything will work just fine.

If you get really stuck, visit the Risk Register settings page where you will find a 'Reset risk workflow' button; clicking that button will return the risk workflow to its original configuration.

Q. Is it possible to visualize the risk exposure values in the Issue Navigator or outside of the issue view itself?

A. Yes. Version 3.0 of Risk Register reveals risk exposure as a custom field, which you can include as a search term in Issue Navigator, and which is available as a sortable column in search results. The exposure level is also shown under 'Risks' on the Project Overview page. Just select a project that has been configured as a risk register, and select 'Risks' from the menu on the left-hand side. The risks are listed in order of highest exposure to lowest.

Q. Is it possible to monitor risks for the IT department as a whole, rather than for a particular project?

A. Yes. Risk Register requires you to nominate one or more projects to act as containers for your risk issues, but there's nothing to prevent you from creating a project specifically to be the One True Risk Register. Alternatively, you could create a projects to act as containers for teams or system areas. You can store your risks in whatever project(s) you like. Since they are essentially a special type of JIRA issue, you have complete freedom to associate them with Epics and Initiatives however you like. The benefit of this design is that each risk will travel along its own workflow independently of the workflow of the issue(s) it is linked to.

Q. Can I associate a risk with multiple business/project issues?

A. Yes. Risks can be associated with other issues via JIRA's built-in issue linking capability. Create your risk issues, and then link them to your other related issues. Remember that the Link item is available in the 'More' menu on the issue view page. One risk can be linked to multiple issues, and a particular issue can be linked to multiple risks.