Risk level tags can be manually adjusted at various stages:
During automated requirement creation = playbook creation: Tags can be changed as needed when a new playbook is created.
During manual requirement creation: Tags can be manually set when a new requirement is first defined.
On Existing Requirements:
Globally (Default Risk Level): The default risk level for a requirement can be modified within its Edit-Prompt area. This change applies to the requirement globally and will be used when adding the requirement into new or existing playbooks.
Within a specific playbook (Playbook-Specific Risk Level): The risk level can be adjusted for a requirement only within the context of a particular playbook by using the label buttons in the requirement's configuration area.
Important: Adjusting the risk level within a playbook does not affect the global default risk level of the requirement.
Example Use Case:
Imagine requirement REQ-001 has a default risk of Medium. It is included in both Playbook 1 and Playbook 2 as Medium risk.
A user can manually change REQ-001 to High risk in Playbook 1 and manually change REQ-001 to Low risk in Playbook 2.
If the user then creates a new, empty playbook and adds REQ-001, it will default to Medium risk (the global default), even though it was manually set to High and Low in the two existing playbooks.