The option "Auto-Reject previous deployments paused in this step on approval" works only within the context of a pipeline execution where it just checks and rejects old executions waiting for approval when their latest step is approved. It does not perform checks on the environment(or any input) configured on the stage. This is currently by design.

Consider a scenario where the environment is passed as an input to the pipeline when executing it.

* There is an execution started with environment "Environment-1 " as the input and this was waiting for approval.

* There was another pipeline that was started after the above execution and it was started with the environment "Environment-2".

Once the execution with environment Environment-2 is approved, the previous execution with Environment-1 shall be rejected .

It appears that when "Auto-Reject previous deployments" is enabled, the inputs passed to the execution are not compared. However, it checks to the service as long as the service is within a CD stage.

The request here is to include and compare the inputs passed to a pipeline before choosing to reject the previous execution. That way pipelines only with the identical inputs are rejected when an approval is made on the latest execution.