Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your feature request, making sure it's handled appropriately.
Prerequisites
[x] I have searched open and closed issues to make sure it isn't already requested
[ ] I have discussed this in #feature-discussion or #backlog and the consensus is that this is something we plan on adding in the near future
[x] I have written a descriptive issue title
[x] I have linked the original source of this feature request
[x] I have labelled the value stream (area/core, area/steps, ...)
[x] I have added the kind/enhancement label
The enhancement
Currently, in the Create Octopus Release in ADO, under the Project field, a user must select a value from the dropdown that's populated from our API. It would be great to allow the use of a variable here as well.
What is the problem this solves or benefit it gives
Being allowed to use a variable here would allow for more robust pipelines from ADO to the Octopus system.
Proposed solution
Allow use of variables from ADO in the "Project" field within our Octopus "Create Release" step.
Workarounds
Use the standard dropdown to select a specific project.
Are you a customer of Octopus Deploy? Don't raise the issue here. Please contact our support team so we can triage your feature request, making sure it's handled appropriately.
Prerequisites
The enhancement
Currently, in the Create Octopus Release in ADO, under the Project field, a user must select a value from the dropdown that's populated from our API. It would be great to allow the use of a variable here as well.
What is the problem this solves or benefit it gives
Being allowed to use a variable here would allow for more robust pipelines from ADO to the Octopus system.
Proposed solution
Allow use of variables from ADO in the "Project" field within our Octopus "Create Release" step.
Workarounds
Use the standard dropdown to select a specific project.
Links
Zendesk Ticket