User story is not back promoted automatically though the 'Back-Promotion Criteria' meets

If you have a connection behavior such that the Back-Promotion Execution is Automated and you have a Back-Promotion Criteria defined as shown in the below screenshot (an example) -

back promotion criteria

The user story (US) will be automatically back-promoted from that environment only if the US meets the criteria before it is available for back promotion.

Scenarios with respect to the above screenshot:

1. You have a US-A with the status In Progress. You deploy this story to the next environment where connection behavior is defined. After the completion of the deployment, the story will be available for back promotion (say to Dev2 and Dev3). Then you change the status to Approved.
You will notice that the automated back promotion behavior will not back promote the story. Though you deploy the story to further environments, the automated back promotion behavior will not back promote the story to Dev2 and Dev3.

This is expected behavior.

2. You have a US-B with the status Approved. You deploy this story to the next environment where connection behavior is defined. This story will automatically get back promoted to Dev2 and Dev3.

What you should do to make the first scenario work?

As of now, you cannot achieve the first scenario with automated back-promotion behavior. However, by updating the Back-Promotion Execution to Scheduled, the first example will work fine.

How did we do?