Updated 6 months ago by Estela García


A release lets you group user stories to promote them together and also keep track of the version of changes that your Salesforce application experiences after every deployment. 

To create a new release, access the Release tab in the Copado Change Management application. If you leave the version field empty, Copado will help you create new tags for your releases after the record has been created.

Once you have created your release, the following visual page will be displayed:

Create a feature branch out of a different branch (not main branch)

As of Copado v11, a new section is added to the release page ("Advanced" section) where users will be able to include a branch which will be used as origin branch to create feature branches. In previous Copado releases, the main branch was taken always by default. Now, it will be the default branch but it is possible to change it.

There is also a  new field in the User Story called "Base Branch", where users will be able to check the branch is being used to create the feature branch.

Version Tagging

Tagging releases helps better track the events when new changes are delivered into Production. As of Copado v11, it will be easier to have a better version control of your releases.

If you create a new release, you will be able to create new values which will apply (1, 1.1, 1.0.1) for your release. The Major value is selected by default. 

From the release detail page, click on "Set version" button. The following page will let you select your release version:

If the previous version is set as Status = "Released", the version values will be automatically calculated to make easier the version assignment.

If your version number has a prefix and/or suffix  (e.g. "v3.43.64-SUMMER"), the following version will include the texts provided and will calculate the next number for the release.

How did we do?