Home > Supervisor Guide > Change > Deployment Tasks > Deployment Tasks
Deployment Tasks are the activities that are completed as part of a Release, for specific Customers, Organizational Units or Everyone when adding a new Item, or updating or replacing an existing Item in the CMDB.
Users who are assigned the Change Process of Release or Deployment are provided access to the Deployment Tasks sub-menu option within Change. These Users can view, and action Deployment Tasks as configured within the Release Team.
The Deployment Tasks tab lists Tasks created within a Release and Users can search Deployment Tasks and edit Tasks that are assigned to them. Tasks can also be exported in PDF or Excel format.
The Deployment Tasks tab defaults to show active Tasks logged in the system. This view can be filtered to show:
Active Deployment Tasks
All Deployment Tasks
My Deployment Tasks.
The list can be re-sorted by clicking on a column header and the number of Tasks displayed per batch, can be altered using the Display pop-up option
Releases can have multiple Deployments that are to be completed at different stages of a Release lifecyle, and to allow for this, multiple stages of the Release Workflow can be defined as Deployment States when creating a Release Workflow. The different Deployment States can be selected as the Deploy Status for a Deployment when a Release is created in the system. Then, as the Release Manager moves through the Release Workflow, by adjusting the Next Action State in the Details tab of the Release, and when a State that is assigned as the Deploy Status for the Deployment is assigned to the Release, the Deployment Tasks move into an active Open State.
When a State that is assigned as a Deploy Status is selected for the Release, the Deployment Tasks for that Deployment created within the Release move to Open and can be actioned by the assigned Technicians. However, if the Control Deployment via RFC is enabled, when the Release moves into the Deployment State, RFCs are automatically created for the Deployment, and only when the RFCs hit the Deploy State configured for the RFC Control within the Details tab of the Release do the Deployment Tasks become active. The Change Manager can view all Deployment Tasks related to the RFC within the RFC Summary screen, and when all Tasks are moved to Closed-Resolved the Change Manager can close the related RFC.
When all Deployment Tasks are completed, the Deployment is automatically closed by the system. When all Deployments are closed for a Release, the Release Manager can close the Release within the Details Tab, by moving the Release Workflow Status to the Exit State.
To edit or process a Deployment Task:
Select Change > Deployment Tasks
Select the relevant
Deployment Task # link
Only Users associated with the Group assigned to the Task can edit
or add details to the Task.
The Summary includes the following information:
Tasks Fields |
Description |
Item Number |
The number used to identify the Item in the CMDB. Click the link to view the Item Details. |
Type |
Details the Item Type of the Item. |
Status |
Shows the stage of the Item Lifecycle applied to the Item at the point of deployment. |
Reason |
Defines if the deployment is to create a new Item, update or replace an existing Item. |
Affects |
Lists the Customers, Org. Units affected by the Deployment Task. If it is Global Deployment, the field will state Everybody. |
Workflow, Team |
Shows the Release Workflow and Team assigned to the Release. |
Manager |
Includes the Release Manager's name. |
Status |
Shows the current State of the Release. |
Group |
Indicates the group of Technicians assigned to Deployment Task. |
Technician |
Shows the assigned Technician, but if multiple Technicians are in the Group, provides a drop down list of all Technicians. The Task can be reassigned here, if required. |
Task Status |
Indicates the current assigned State for the Deployment Task. The options are:
When the Release Workflow is an non-Deploy State, the Task will be locked at Pending. When the Release moves to a Deployment State, the Task automatically moves to Open. |
Next Status |
Allows the Technician to move the Task from Open to Closed-Resolved, when the Task has been completed. |
FSC Date |
This can be completed by the Technician to set the Forward Schedule Date for the Task. However, once the Task is moved to Closed-Resolved the field will be automatically populated with the Closed time and date. |
Click Edit
Adjust information recorded in the Summary tab.
Click Save.
The Notes tab allows Users to create Notes for updates regarding a Deployment Task. To view any Notes listed within the Notes Tab, click on the Note Number hyperlink.
To add a Note:
Click
The Task opens in Edit mode and the new Note screen is visible
Enter the Note details
Enter
Note Time
The time entered represents the amount of time accumulated to formulate
the Note's content. If no additional time has been spent on the Task
away from the application, leave this field blank, as the system calculates
Logged Time when the request is in Edit mode. (See: Contracts
Logged Time.)
Adjust the time and date work was completed, if required
Click Save.
Use the Draft button to save an incomplete Note entry, which will be displayed in the Notes list. If the Fast Note button is selected when a draft Note has been recorded against a Task, a warning will be displayed. To continue working on a draft Note, open the request in Edit mode and select the Note No. hyperlink.
The Audit Trail tab records all changes and updates for the Deployment Task and lists who they were made by. The list can be exported by selecting the export to PDF icon.
To view an audit trail entry within the Deployment Task Summary tab:
Select
the Audit Trail tab
Click on the identification number hyperlink to display the entry details
Click
Cancel.
The expanded window is closed.
To review examples of Release and Deployments, refer to Release Management Applied.