Feature request to have a  way to define dependencies between deployment environments within the same deployment project. The main goal is to enforce a strict deployment order. For example:

Do not allow deploying to Environment A (e.g. Production) Unless the same release has already been successfully deployed to Environment B (e.g. Test/QA)

In other words, we would like to be able to configure that an environment "depends on" another environment, so that Bamboo blocks or prevents a deployment to the dependent environment if the prerequisite environment has not yet received that exact release (or has not succeeded).

Desired capabilities (high level):

A configuration option on a deployment environment to declare one or more "upstream" environments it depends on.

Validation that a given release has been successfully deployed to all required upstream environments before it can be deployed to the dependent environment.

Clear UI feedback when a deployment is blocked because dependencies are not satisfied (e.g. tooltip, message in the deployment dialog, audit entry).

Ideally, this would work without custom scripts, manual checks, or external tooling.

This feature would make it much easier to enforce consistent promotion workflows (e.g. Dev → Test → Staging → Production) and reduce the risk of accidentally deploying untested releases directly to higher environments.

We can achieve a strict deployment order to ensure Production never sees a release that hasn't cleared QA by using After successful deployment trigger.While triggers automate the flow, they don't inherently stop a user from clicking "Deploy" on Production manually.