Upcoming changes to the Pipelines promotion workflow

[#1]

We’re announcing an important update to the deployment dashboard in Bitbucket Pipelines. As part of our ongoing efforts to make deployments more flexible and user-friendly, the promote action on the deployment dashboard will be deprecated and become unavailable on 1 Dec 2025.

From the deployment dashboard, you can continue to deploy to an environment by navigating to the linked pipeline and selecting the Deploy button on the required step. This ensures you still have full control over your deployments, while providing us with increased flexibility to further enhance our deployments feature in the future.

This change is part of an initiative to break down the current Deployments functionality into more modular and granular capabilities. Our goal is to provide you with greater control and a more streamlined experience when managing your deployments.

For more details on these enhancements and our vision for the future of deployments in Bitbucket Pipelines, we encourage you to read our latest blog post: Evolving deployments in Bitbucket Pipelines: Concurrency Groups and Environments - Work Life by Atlassian.

We appreciate your understanding and support as we continue to improve Bitbucket Pipelines and deliver a more flexible deployment experience for all users.

[Bruce Song]

We found this quite inconvenient after the change. Can we provide an API to deploy a specific step in the pipeline? So we can use the API to make this simpler

[Bikash Karki]

Discontinuity of the Promote button from the deployment section has been hampering the productivity and ability to track the merged ticket on the current version very difficult. When moving to pipeline and trying to promote we do not see the old tickets that were merged on earlier builds. This is very annoying. Better come up some newer method to at least let us able to track all the merged tickets up to that point.

[Brian Bistolfo]

You now have to click on the pipeline itself (which you can do from your Deployments page), and from there you can access the "Deploy" button for a given step. This will still bring up the usual confirmation modal which includes tabs to view the env-level diff by ticket, PR, commit, and code.

Not a big deal, just annoying.