User Stories - Deployment Tasks

Updated 1 month ago by Copado Solutions

Deployment Tasks Overview

A deployment task is an action you can add to a user story for it to be executed every time the user story is deployed to an org. This task is added to the deployment record as a deployment step and it’s positioned either before or after the Git Promotion / MetaData deployment step. Depending on the kind of action you want to execute, there are several types of deployment tasks you can create together with their equivalent deployment steps:

  1. Manual Task
  2. Data
  3. Bulk Data
  4. Delete MetaData
  5. Custom Setting
  6. Apex
  7. URL Callout

When a user story is deployed to the next environment, the tasks included in that user story will be converted into the equivalent deployment steps.

You can add several deployment tasks to a user story. The list of user story tasks will show Order, Type and Status fields, and tasks will be sorted by order (as of v10).

Copado also allows you to add attachments to the deployment tasks. This way, it is easier to find related attachments when all tasks are combined in a promotion.

The Owner field in manual deployment tasks allows you to assign the task to a user, that can be notified via chatter, email or both, so your deployments won't get stuck again waiting for a manual intervention!

How to Create a Deployment Task

To create a deployment task, follow the steps below:

  1. Navigate to a User Story record.
  2. Click on Related and navigate to the Deployment Tasks related list.
  3. Click on New and select an option from the Type drop-down menu.

  1. Fill in all other relevant fields and click on Save.

Deployment Tasks Order

When you add several deployment tasks to a user story, each task will have an order number, which indicates the order in which they will be executed once the user story is deployed. When you have multiple user stories with deployment tasks in a promotion, the order will be based on the user story number, that is, the tasks in the user story with the lowest number will be executed first. Let’s take a look at the chart below to see how this works:

As you can see in the chart above, when the promotion deployment is executed, the user story tasks are converted into deployment steps. These steps are then deployed following the user story merge order and the deployment task order within each user story. The tasks from US-0000005 get deployed first and those from US-0000010 get deployed last.

Please note that, in order to use this feature, you need at least read permissions in the Deployment Task object and proper FLS in the dataJSON__c field of the Deployment Task object.


How did we do?