Override User Story Promotion Merge Order

Updated 3 weeks ago by Copado Solutions

By default, user stories get merged into the promotion branch based on the User Story Reference field in ascending order. However, Copado allows you to override this criteria and define your own merge order criteria.

In the Pipeline or Promotion record, there is a field called Order User Stories by where you can specify a user story field with ascending or descending order that will be used to define the merge order.

Pipeline

Promotion

If the field Order User Stories by in the Pipeline record is not empty and this field is empty in the Promotion record, the promotion will inherit the value specified in the Pipeline record. If both fields are empty, then the default order will be applied (User Story Reference field in ascending order).

For example, if you have three user stories (US-0009, US-0001, US-0006), by default, they will be merged in ascending order like this: US-00001 > US-00006 > US-00009.

You can leverage the Priority field on the user story to define a custom merge order, or you can also create your own custom field.

If, for instance, you use the Priority field, go to the Pipeline or Promotion record and type Priority__c asc in the Order User Stories by field. Open the three user stories and add a value to the Priority field (US-00001.Priority__c = 3, US-00006.Priority__c = 1, US-00009.Priority__c = 2). Once you create the promotion deployment, the user stories will be merged in this order: US-00006 > US-00009 > US-00001.


How did we do?