We have several pipelines set up where we sometimes want a configuration to auto-promote based on a variable, but would also like users to be able to promote that configuration manually. Currently we end up duplicating the promotion, once with "Auto Promote" checked and a build condition that requires a variable to be set, and once without "Auto Promote" and no build condition (other than a successful build). This leads to errors where we forget to update both promotions (to add a new variable, for example) and confusion for users when they see two similar promotions available.

It would be nice if "Auto Promote" had conditions attached to it similar to the "Execute Condition" on steps where we could use a script, a variable, or other similar conditions to determine whether or not to auto-promote. This would allow us to use the same promotion for both cases and avoid duplicating them.