1 customer discovered, workaround to create a custom lifecycle
Version
2021.3.12258, 2024.3.4944
Latest Version
None
What happened?
When you have a project that uses the default lifecycle and you attempt to create a scheduled trigger, the destination is filtered to either the enviromment selected or the next one in the default lifecycle phase.
In the below screenshot the default lifecycle has the following:
When you attempt to make a new trigger and select one of the environments as the destination, it will only give the current one and the next one, or any nested enviroments (Prod in this case as shown above):
Reproduction
Create any new project using the default lifecycle
Attempt to create a trigger
Set any environment as the source
Try to select any environment as the destination and observe the filtered list
Error and Stacktrace
No response
More Information
If you use a non-default lifecylce and add scoped/unscoped phases in different positions it allows you to select all environments. Feels like this behaviour should be reflected in the default lifecycle as well since you don't setup any phases for this.
Workaround
Creating a new lifecycle with a single, unscoped phase achieves the outcome of being able to select any environment in either dropdown.
Also, the API will accept any environment, you can update the environment Id in the Action.DestinationEnvironmentId to the intended environment and the trigger will update with that value.
Severity
1 customer discovered, workaround to create a custom lifecycle
Version
2021.3.12258, 2024.3.4944
Latest Version
None
What happened?
When you have a project that uses the default lifecycle and you attempt to create a scheduled trigger, the destination is filtered to either the enviromment selected or the next one in the default lifecycle phase.
In the below screenshot the default lifecycle has the following:
When you attempt to make a new trigger and select one of the environments as the destination, it will only give the current one and the next one, or any nested enviroments (Prod in this case as shown above):
Reproduction
Error and Stacktrace
No response
More Information
If you use a non-default lifecylce and add scoped/unscoped phases in different positions it allows you to select all environments. Feels like this behaviour should be reflected in the default lifecycle as well since you don't setup any phases for this.
Workaround
Creating a new lifecycle with a single, unscoped phase achieves the outcome of being able to select any environment in either dropdown. Also, the API will accept any environment, you can update the environment Id in the
Action.DestinationEnvironmentIdto the intended environment and the trigger will update with that value.