A system generated issue will be triggered as a result of a RAG change, this may be off the back of a user invoking the suspend action or invoking the backout.

There are three basic mechanisms for creating user-generated issues:

1) Task Level: Issues arising as a result of the suspension of a task during the execution phase. This action would typically be performed by either the task owner or the Runbook Deployment Manager. Issues of this type are created from the Task Detail screen (408) only, as shown in the image below.

1. 2) Runbook Level: Issues can also be raised at the Runbook level and are not associated with a specific task. This action would typically be performed by the Runbook Deployment Manager. To invoke this functionality you can select the Issues screen

Select the Suspend Runbook option and fill in the required data. Once this is done, click Raise Issue

3) Event Level: Issues can be raised at Event level and are not associated with a specific task or runbook. This action would typically be performed by the Event Lead. To invoke this functionality from the Event ... More Options menu select issues. This will launch the Event Issues

1. Issues can also be raised at the Runbook level and are not associated with a specific task. This action would typically be performed by the Runbook Deployment Manager. To invoke this functionality you can select the Issues screen

This will take you to the Event Issue page, from here you can Raise an Event Level Issue. The Event Level Issue modal will launch allowing you to enter information with regards to the issue for the Event.