Administering the application (Data Center)
At a glance: Configure Risk Register administration settings in Jira to set up risk fields, issue types, screens, controls, treatments, workflows, risk models, risk registers, and support resources.
This guide is for Jira administrators who configure the Risk Register app after installation. Follow it to understand each administration page and the Jira configuration areas that support risk management in your site.
Before you begin
Make sure you have Jira administrator permissions. Some actions open Jira administration pages for custom fields, issue types, screens, issue links, and workflows.
Open Risk Register administration
In Jira, select the gear icon in the top-right corner.
Select Manage apps.
In the left navigation, go to Risk Register.
The Risk Register menu shows the administration pages described in this guide.
Use the Getting started page
The Getting started page appears after you install Risk Register. Use it as a setup checklist while you configure the app.
Configure Settings
Use Settings to configure the Jira components required by Risk Register.
Fields
Use the Fields tab to configure app-specific Jira custom fields.
Select a field to open its Jira custom field configuration page.
For field details, see Creating and Editing Risks.
For Jira custom field administration, see Configuring a custom field.
Issue type
Use the Issue type tab to choose which Jira issue type represents risks.
Select Create issue type to create a new Risk issue type.
Select Manage issue type to open Jira issue type administration. For more information, see Adding, editing, and deleting an issue type.
Screens
Use the Screens tab to define the screen scheme Risk Register can use when users create, edit, and view risks.
A Risk Register project can use any screen scheme. If a project does not use the scheme configured here, Risk Register shows a warning on the project settings page.
Select Create, Edit, or View to show the fields for that screen.
Use the slider beside each field to enable or disable the field on that screen.
Select Configure screen to open Jira screen configuration. For more information, see Defining a screen.
Select Create screen scheme to create the screen scheme required by the app. This does not change existing screens.
Select Manage screen schemes to open Jira screen scheme configuration. For more information, see Associating a screen with an issue operation.
Controls
Use the Controls tab to configure how risk controls appear and behave in the app.
Choose whether empty cells in the risk matrix appear grey or use the relevant risk colour.
Choose whether Impact or Probability appears on the horizontal or vertical axis.
Select Flip to swap the matrix axes.
Choose whether users set risk values with a drop-down or a slider on create and edit screens.
Treatment
Use the Treatment tab to select the issue link type that connects treatments to risks.
When the relationship is configured, treatments appear beneath risks on the risk register page. For more information, see Viewing Risk Registers and Matrices.
Select None if you do not want treatments to appear on the risk register page.
Select Manage issue linking to open Jira issue linking configuration. For more information, see Configuring issue linking.
Workflow
Use the Workflow tab to select the default workflow type for risks.
Your Jira administrator must still associate the workflow with the relevant projects and issue types. Risk Register notifies you when a project is not using the workflow specified here.
Select Create workflow type to create a workflow suitable for Risk Register.
Select Manage workflows to open Jira workflow administration. For more information, see Working with workflows.
Recommendation: Do not modify the risk-specific workflow created by Risk Register. It triggers internal app functions required by the app.
You can use a custom workflow with Risk Register if it is appropriate for your Jira configuration.
Configure risk models
Use Risk models to define how risks are assessed.
A risk model is a matrix with Impact and Probability axes. Each cell defines a risk level. You can create multiple risk models and assign them to different projects.
Note: At least one risk model must remain available as the default risk model.
Review the model list
The model list shows all risk models in your Jira site and the projects each model applies to.
The icon beside each model indicates its status:
A green smiley indicates that the model is configured correctly.
A yellow band-aid indicates that the model requires attention.
From the model list, you can:
Select Run health checks to check whether your risk models work correctly.
Select Add a risk model to create a risk model.
Select a risk model name to open the model editing screen.
Edit a model
The model editing screen includes title bar icons for common actions.
Select the green smiley or yellow band-aid to open the health check screen.
Select the pen icon to rename the model.
Select the trash icon to delete the model.
Assign projects
The line below the model title shows which projects use the model.
Select the project line to add a project.
Select the x next to a project name to remove that project from the model.
Manage risk levels
Use the Risk levels drop-down to view and manage the risk levels defined for the model.
Select the edit icon to change a risk level name or colour.
Select the trash icon to delete a risk level.
Select Add a level to create a risk level and define its name and colour.
Configure the matrix
Use the matrix configuration area to define the risk matrix.
Select the drop-down arrow in a matrix cell to change the risk level for that cell.
Select the trash icon in a row or column header to delete that row or column.
Drag the vertical or horizontal bars to reorder rows or columns.
Select a row or column title to rename it.
Select Add col to add a blank column.
Select Add row to add a blank row.
Select Flip matrix to swap the Impact and Probability axes for the model.
Run health checks
Select the green smiley or yellow band-aid in the risk model title bar to open the health check screen.
The health check screen shows whether the custom fields required by Risk Register are configured correctly.
Note: The health check screen is intended for experienced Jira administrators. Problems shown here are usually caused by changes to the custom fields used by the app.
Manage risk registers
The page lists the risk registers that you have permission to administer.
If no registers have been added, the page displays No risk registers have been created yet.
Add a risk register
To add a risk register to a project:
Select Add a register.
Select a project from the Project list.
Choose how Risk Register should handle the project configuration:
Automatic
Manual
Select Create.
Projects that already have a risk register are not available for selection.
Automatic project configuration
Select Automatic to apply the recommended project configuration where it is safe to do so.
Risk Register checks the project configuration and applies available fixes. It does not automatically make a change when that change could affect other projects, such as modifying a shared Jira scheme.
Automatic configuration is selected by default.
After creating the register, Risk Register checks the project again and reports whether:
The project is properly configured.
Potential configuration problems remain.
Select properly configured or potential problems in the result message to open the project’s Risk Register settings.
Manual project configuration
Select Manual to create the risk register without automatically changing the project configuration.
You can then review and apply each recommended change from the Risk register page in the project settings.
Use this option when you want to control changes to:
Issue type schemes
Screen schemes
Field configurations
Workflows
Other project settings used by Risk Register
Review the creation result
While the register is being added, the page displays Creating risk register.
After it has been created, the page displays Risk register created and the result of the project configuration check.
When the project is properly configured, you can:
Select properly configured to review its settings.
Select View risk register to open the new project risk register.
When potential problems remain, select potential problems to review the configuration report and available fixes.
You can add another register without closing the creation panel. Select Cancel to close the panel.
Work with an existing risk register
Select a risk register in the list to open its action menu.
The following actions are available:
View
View settings of
Remove
View a risk register
Select View to open the risk register in its Jira project.
From the project risk register, you can review risks in the register or matrix view and add new risks.
Configure a risk register
Select View settings of to open the project’s Risk register settings page.
The project settings page checks whether the project uses the recommended Risk Register configuration. Depending on your permissions and the project’s Jira schemes, you can review or correct its:
Risk issue type
Screens
Custom fields
Workflow
Other required project configuration
Some changes may affect shared Jira schemes. Review the affected projects before applying a change to a shared scheme.
Remove a risk register
To remove a risk register:
Select the register in the list.
Select Remove.
The register is removed from the list and Risk Register is disabled for that project.
Removing a risk register does not:
Delete the Jira project.
Delete issues previously created as risks.
Remove Risk Register custom fields from Jira.
Reverse changes previously made to the project’s Jira schemes.
The existing issues remain in Jira as ordinary issues. You can add a risk register to the project again later.
The application removes the register immediately when you select Remove. The Risk registers page does not display a separate confirmation dialog.
Why a project is not available
A project may not appear in the project selector when:
It already has a risk register.
You do not have permission to administer its risk register.
The project has been deleted or is otherwise unavailable.
After you remove a project’s existing register, the project becomes available for selection again.
Review attribution
Use Attribution to view the third-party software components used by the app.
View release notes
Use Release notes to view recent changes to the app.
Open the FAQ
Use FAQ to open the frequently asked questions list.
Get support
Select Get support to open the ProjectBalm support portal. Use the portal to search the knowledge base or raise a service request.