Raise Issue - Suspend Task

Users can Raise an Issue by Suspending a Task.  Any available or active tasks in the 'Implementation Phase' of an Runbook can be suspended by the Deployment Manager.  Users of Author or Manager authorisation level can only suspend tasks that they are the owner of or tasks that are aligned to their team.

Suspend Task

To Suspend a Task and Raise an Issue, Users must be on the Task Detail screen (408) and navigate to the Issues Tab. From here (ie. by selecting that Task from the List Tasks screen).

 

Click the Raise Issue button, which will launch the Raise Issue Modal Window. On the Modal Launching opt to Suspend Runbook.

The following list describes the various fields that can be populated on the Create Issue screen within ICEFLO.  Note that fields with the red asterisk are mandatory, the others are elective.

Remember to click the Apply button after filling in all of these fields.

1) Type: ICEFLO assigns a Type to each issue, selected via the drop-down box from the following list:

  • Technical Activity
  • Technical Verification
  • Business Verification
  • End User Access
  • Logistics
  • Unknown

2) Title: A free-form text field that enables the user to give the issue a brief title. This title will appear on the List Issues screen and should be as concise as possible.

3) Severity: ICEFLO assigns a severity to each issue, selected via the drop-down box from the following list:

  • Low
  • Medium
  • High

4) Owner: The Issue Owner is the user who raised the Issue, typically the ICEFLO Deployment Manager or task owner, but in certain circumstances it could be an Issue Manager.

5) Est. Resolution Time: This is a mandatory date and time attribute that must be provided when an issue is created to Suspend a Task:

  1. The date and time is populated using the date-picker icon
  2. The definition of the <Estimated Resolution Time> is the revised time when the associated task is expected to be completed
  3. It therefore should include diagnostic and rework time for the task
  4. If the estimated resolution time is not known when the issue is created, it is recommended that the <Estimated Resolution Time> is aligned with the current forecast end time of the task.  When the <Estimated Resolution Time> is superseded by the current system time (i.e. 'now') it rolls forward in real time
  5. This key field can be updated at any time using the Maintain Issue screen by the task owner, Deployment Manager or Issue Manager.

IMPORTANT: The <Estimated Resolution Time> may have a direct and immediate impact on the overall forecast end time for the Runbook and any other Runbooks which are inter-dependent. As such, great care should be taken when setting this attribute as it may result in changes to the overall RAG status (with associated escalation comms). The <Estimated Resolution Time> will also push out the start and end times of any dependent tasks and any tasks in that dependency flow.

6) Description: A free-form text field that enables the user to give the issue a detailed <description>, elaborating on the information provided in the <Issue Title>..

Remember to hit the Raise Issue button after filling in all of these fields. Raise and Close is not an option when suspending a Runbook.

Suspended Task

By reverting to the Task Detail screen, you can view the key difference between a 'Suspended Task' and a 'Suspended Runbook'.

After Suspending a Task, the Runbook has remained in an 'Active' state and tasks succeeding the 'Suspended Task', can still be activated and completed.

Issues

On the Runbook - Issues screen you will see the Issue listed and note that it has a Task associated to it.