...
These dropdown menus determine which issue types when and how various options are presented to users:
Note the following:
If an issue has a risk assessment attached to it, no matter what its issue type, that issue will appear in the risk
...
registers based on those projects, subject to the settings of those risk registers.
If
...
the issue
...
is
...
of the primary risk type, then it always
...
has a risk
...
assessment attached to it. In the example above, issues of type
...
Story
...
will always appear in a risk register.
...
New issues that have are of one of the supplementary risk types don’t have risk assessments attached to them by default, but you are able to add risk assessments to them. You can define the supplementary risk types by inclusion or exclusion using the "Only" and "All except" options. In the example above, you will be able to add a risk assessment to issues of type
...
Task
...
will appear in the risk register if someone has added a risk assessment to them.
...
If an issue is neither of the primary risk type nor one of the supplementary risk types, then it’s not possible to add a new risk assessment to it.
If an issue was once a primary risk type, or if it was once a supplementary risk type and the user added a risk assessment to it, then it will continue to appear in relevant risk registers even if the project/app settings changed to that it no longer is of the primary risk type or a supplementary risk type.
- The primary risk type and supplementary risk types defined here represent defaults. Particular projects can override these defaults.
Risk treatment
This dropdown allows you to nominate an issue link type that defines how treatments are connected to risks. When this relationship is defined, treatments will appear beneath risks on the risk register page (see Viewing Risk Registers and Matrices). If you leave the field blank, then treatments will not appear on the risk register page.
...