Configure a risk register for a project (Data Center)

Configure a risk register for a project (Data Center)

At a glance: Enable risk management in a Jira project, then confirm that the project uses the recommended issue type, screens, fields, and workflow for Risk Register.

This page explains how to configure a Jira project so it can be used as a risk register.

Applies to: Risk Register for Jira. Some steps require Jira administrator permissions because they change shared Jira schemes or app settings.

Before you begin

Make sure that:

  • Risk Register for Jira is installed and licensed.

  • A Jira administrator has configured the Risk Register app settings.

  • An issue type has been nominated to represent risks.

  • You have permission to administer the project.

For detailed administration guidance, see Administering the Application.

Enable risk management

To enable a risk register for a project:

  1. Open the Jira project.

  2. Select Project settings.

  3. Select Risk register.

  4. Turn on Enable risk management for this project.

Risk Register creates a project risk register and displays a configuration checklist.

Review the configuration checklist

The checklist verifies the following project settings:

  • Issue type: The nominated risk issue type is available in the project.

  • Screens: The risk issue type uses the recommended screen scheme.

  • Fields: The fields required by Risk Register are visible and available.

  • Workflow: Risks use the workflow recommended in the Risk Register app settings.

A check mark means the project is correctly configured. A warning means the project does not use one of the recommended settings.

Configure the risk issue type

The Issue type section checks whether the issue type nominated for risks is available in the project.

If the issue type is already available, no further action is required. If it is missing, choose one of the available options:

  • Add issue type to scheme adds the risk issue type to the project’s current issue type scheme.

  • Add to shared issue type scheme updates a scheme that is also used by other projects.

  • Create a new issue type scheme creates a separate scheme for this project.

Shared scheme warning: Updating a shared issue type scheme affects every project that uses the scheme. Create a new scheme when the change should apply only to the current project.

If no issue type has been nominated for risks, ask a Jira administrator to nominate one in the Risk Register app settings.

Configure the risk screens

The Screens section checks whether the risk issue type uses the recommended screen scheme.

When the project uses a different screen scheme, choose one of the following options:

  • Modify issue type screen scheme maps the risk issue type to the recommended screen scheme.

  • Modify shared issue type screen scheme updates the scheme for every project that uses it.

  • Create a new issue type screen scheme creates a separate issue type screen scheme for the current project.

The recommended screens provide the fields required to create, edit, view, and assess risks.

Check the risk fields

The Fields section checks that the fields required by Risk Register are visible.

These include the fields used for risk assessment, such as:

  • Probability

  • Impact

  • Inherent risk

  • Residual risk

  • Treatment

When a required field is hidden, Risk Register identifies the affected field.

Depending on the project configuration, you can:

  • Select Modify field configuration to correct the current configuration.

  • Select Modify shared field configuration to update a configuration used by multiple projects.

  • Select Create a new field configuration to create a separate configuration for this project.

  • Follow the link to the project’s field configuration and check the field configuration and custom field contexts manually.

Make sure each Risk Register custom field has a context that includes the project and the nominated risk issue type.

Configure the risk workflow

The Workflow section checks whether risks use the workflow recommended in the Risk Register app settings.

When the project does not yet contain risk issues, you may be able to select:

  • Modify workflow scheme

  • Modify shared workflow scheme

  • Create a new workflow scheme

When risk issues already exist, modify the project’s workflow scheme manually and map the risk issue type to the recommended workflow.

To change the workflow manually:

  1. From the project settings, select Workflows.

  2. Edit the workflow scheme used by the project.

  3. Map the nominated risk issue type to the recommended risk workflow.

  4. Publish the workflow scheme.

  5. Complete any requested status mappings.

Workflow migration: Changing the workflow for existing risks may require Jira to migrate the issues between workflows.

Confirm the project is ready

Return to Project settings > Risk register after making your changes.

Confirm that each checklist section shows that the project is correctly configured:

  • The nominated risk issue type is available.

  • Risks use the recommended screen scheme.

  • All essential fields are visible.

  • Risks use the recommended workflow.

You can now create risks using Jira’s standard Create action and selecting the nominated risk issue type.

Disable risk management

To remove the project risk register:

  1. Open the project.

  2. Select Project settings > Risk register.

  3. Turn off Enable risk management for this project.

Disabling risk management removes the Risk Register project configuration. It does not delete the Jira issues that were created as risks.