Deploy latest release trigger restricting deployments to environments in initial lifecycle phase #9810
Description
Severity
Sev-3 (discovered internally)
Version
Unsure exactly, but potentially as far back as 2019.2.0.
Latest Version
I could reproduce the problem in the latest build
What happened?
When creating a trigger to deploy the latest release, the list of target environments is restricted to those belonging to the first phase of the relevant lifecycle, regardless of whether it is optional or not. This differs from manual deployments, where deployments can be made to any environments belonging to the first n+1 phases, given that the first n phases are optional.
Reproduction
- Create a new lifecycle with three phases, each with an associated environment and with no environments shared between phases.
- Mark the first two phases as optional.
- Setup a "Deploy Latest Reelease" trigger for a project for the given lifecycle.
- Note that the environment dropdown is restricted to a single environment (belonging to the initial phase).
More Information
Discovered internally.
As far as I am aware, no customers have reported this discrepancy as of writing.