Status of Promoted User Story record getting changed to Outdated and User Story unavailable for Back promotion

Let us consider a simple pipeline as the below setup:

User-added image

You have deployed a User Story from Dev 1 to UAT (by Promotion record P-0001) and then from UAT to Production (by Promotion record P-0002). Ideally, you wish to see this User Story available for back promotion from UAT to Dev 2 and from Production to Hotfix.

However, after the Winter ‘21 release, there is a concept of status of the Promoted user Story getting changed to Outdated and that controls which User Story is available for Back Promotion.

Let us consider two scenarios in the above pipeline:

  1. After deploying to a higher org, let’s say, till Production and you manually change the Environment to UAT, then the Promoted User Story record related to P-0002 will have the status changed to ‘Outdated’. At this point, Copado will assume that the US is sitting at UAT and hence will make it unavailable for back promotion from Production to Hotfix.
  2. After deploying to a higher org, let’s say, till Production and you manually change the Environment to Dev 1, then the Promoted User Story records related to P-0001 as well as P-0002 will have the status changed to ‘Outdated’. At this point, Copado will assume that the US is sitting at Dev 1 and hence will make it unavailable for back promotion from Production to Hotfix as well from UAT to Dev 2

Do note in the first scenario, the User Story will still be available for back promotion from UAT to Dev 2.

Additionally, at times, we might encounter a scenario while performing Step #1 above i.e. changing the environment from Production to UAT but the status of both the Promoted User Story records related to P-0001 and P-0002 gets changed to Outdated incorrectly, whereas only the status for P-0002 should have changed ideally. This introduces an undesired change because the User Story is now no longer available for back promotion from UAT to Dev 2 either. Do note that this is a Known Issue and the bug has been fixed in v17.8. You can get more details about the issue over here: https://success.copado.com/s/known-issue/a9j5p000000oLrQAAU/ki00368

If you are encountering this bug, upgrading to v17.8 will solve the issue.


How did we do?