Configuring Global Options and Risk Schemes
- Bruno Marotta
- Angelica Salazar
- David Sedlock
Overview
easeRisk for Jira is configured using global options and Risk Schemes. A Risk Scheme is a collection of configuration options that can be shared among multiple projects. The use of Risk Schemes reduces the setup effort and ensures that Risk Management practices are applied uniformly in your organization.
Global Configuration
easeRisk comes with global configuration options which are determined by Jira administrators. To access the configuration options, go to Jira Administration > Manage Apps > easeRisk for Jira > Configuration.
Activate Risk Management for All Projects | By default, easeRisk is enabled for all projects, making it is accessible to all projects via the Project sidebar. If disabled, it is only available to projects that are explicitly associated with a Risk Scheme. |
easeRisk Administrators | If no groups are specified all users are allowed to administer Risk Schemes. Otherwise only the users in the specified groups (and Jira system administrators) are allowed to do this. An “easerisk-administrators“ group is automatically created when the application is installed. We recommend assigning selected risk managers to this group and using it for this option. |
Risk Scheme Configuration
A Risk Scheme collects together the following options:
Which issue types and link types are used to represent risk and measures.
Which fields are displayed by default in the Risk Register.
data center only A set of Risk Formulas to be calculated automatically.
A set of Risk matrices to be displayed in the Reports menu of Boards where the associated project is included.
A set of Quick filters to be displayed in Boards where the associated project is included.
A set of Assessment Criteria to explain to other users how the risk values are interpreted.
When the application is installed a Default Risk Scheme is created. When the global option Activate Risk Management for All Projects is enabled, this scheme is automatically associated with all projects that do not have a Risk Scheme explicitly associated with them. You are allowed to rename this scheme, but you cannot delete it.
As a good practice, we recommend only creating additional Risk Schemes if necessary, thus ensuring that your enterprise risk management process remains simple and consistent.