1. Backout (BO) Triggers - No Trigger Set:  This Flag  indicates that no BO trigger has been set for this Task.  This Flag will always be present.  

BO Triggers - Trigger Set:  when a Backout Trigger has been set the icon will resemble the No Trigger set but without the cross in the arrow, to indicate that a BO Trigger has been set.  (You will recall that a BO Trigger is used to link a  Task or Tasks in an Implementation Phase (eg. bring down application) with the opposite Task or Tasks in the Backout  (eg. bring up application) in order to reverse the effect of the Implementation Task(s).

2. Communications:  The Speaker indicates that Communications have been set on this task. There are two types of Communications which can be applied. 

Notify Owner - where the Owner of the Task will receive a text to email advising that their task is ready for Activation

Trigger Comms - where users in the Deployment Team will be notified when a Task has been completed.

More information can on Communications can be found - Runbook Communication

3. Milestone:  The Flag icon indicates that a Task is deemed a milestone task - a significant Task within your Runbook. On the Runbook Gantt Chart, Milestone Tasks will show as a yellow bar.

4. Explicit Start Time:  The Clock indicates that a Task has been given an Explicit Start Time, i.e. it cannot be activated before this time, regardless if Predecessor Tasks have been completed.

5. Note(s) added:  The notepad icon indicates that at least one note has been added to a Task.  Be aware that notes are recorded against specific Tasks and will only be Cloned when cloning a Runbook,  if Clone Notes is selected.

6. Document(s) added:  The Document indicates that at least one document has been attached to a Task. Documents can also be selected to be Cloned when cloning a Runbook.

The Task Dependency Flag has a float over function, meaning that when Users float over the Dependency Flag, they will be provided with a summary of a Task's dependencies.  If a Task's Predecessor or Successor is a Task in another Runbook  the Runbook ID and Name will be listed and the Dependency flag will be red.

Tasks which are Linked to Predecessors will be a navy link. Tasks which have had an explicit Dependency set across Stages within an Runbook will be a yellow link. A broken link depicts dependencies on the task.

Dependencies cannot be made across Phases in a single Runbook.