Remember: CRM - Tasks Automation and child pages

How-to

Copado provides built-in functionality for tasks automation, which is the object Deployment Steps.

The object deployment step is linked to the User story record, and when created is always added as part of the deployment of the story.

This sounds familiar, right? Currently, the Manual Steps added in Jira are automatically synched to Copado in shape of Deployment steps with the type of "Manual Task", but there are many other types of deployment steps that are automated.

Creating a Deployment Step

Select the type of step

Information of each of the steps can be seen here https://docs.copado.com/articles/#!copado-ci-cd-publication/deployment-steps.

The recommendation is to use:

• Apex: It allows to execute an apex anonymous script in the destination org of the deployment automatically in the deployment. See existing apex templates in this page. (TODO).
• Salesforce flow: Same as Apex but using a flow
• URL Callout: This includes built-in automations from copado such as installing a package in a target org. 

Others can be explored, but relying in the first three mentioned is typically easier and faster. For example, custom setting type is not necessary given we can do this through an Apex script and it's included as part of the template.

Add other relevant information

Important - For the deployment steps:

• In the title, follow the contention: "<COPADO-KEY>: <JIRA-KEY> - <STEP TITLE>". See example above
• These steps will be added before or after the git metadata depending on the custom field Order).
• We can configure for which orgs these should be executed in the deployment or not, using the multi-select picklist Environments, by default these apply to all orgs)

When to create a Manual Task and not Automated

For tasks that can be automated in less than 30 minutes, these should be automated.

In other cases in which the automation is more complex, it may be more pragmatic to rely on human action.