OctopusDeploy
Scoped Prompted Variables with Multiple Values (and scopes) Ignore Scope Specificity and Show Multiple Prompts
Severity
No response
Version
2025.3.12060
Latest Version
I could reproduce the problem in the latest build
What happened?
When configuring a required prompted variable with multiple values in a Variable Set(or project variables) with both an unscoped value and a value scoped to a specific environment, Octopus prompts for the variable twice during deployment to that environment.
Reproduction
-
Create 1 Variable and select the “Prompt for value” option -
Set the “Control Type’ value of “Drop Down” -
Configure your Drop Down values -
Select the “Required” option at the bottom -
Select “Done” to create the new variable -
In this new Variable, select the option to Duplicate Value -
Edit the new Value to have different Drop Down Options -
Save the new Variable Value -
Scope this new Variable value only to Environment “A” -
Create Release and Deploy to Environment "A"
Error and Stacktrace
More Information
No response
Workaround
Having scoping for each prompted value. Or set a default value for the unscoped prompted variable value instead of using an unscoped value
The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email [email protected]. Knowing how many people this issue affects helps us determine its priority.
