Worker pools only are compatible with two OOTB Octopus process steps (deploy a script, deploy to cloud). My team heavily uses the 'Deploy a Package' step, but this step is not allowed to use worker pools. This is quite an oversight and should be a prioritized feature in the next sprint.

Allow the default values for prompted variables to be calculated, instead of a constant.

Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.

Optionally provide a friendly interface (date picker control) for the respective values.

if we can have date filter in the task section then it will be ease to get the data for a particular time period.

TASK ---->Advanced Filter

In some previous version of Octopus, I was able to do this. I always used the search dropdown to open up multiple projects at a time using middle mouse button click.

There is currently no way to associate a project to multiple tenants without going into each tenant one by one, finding the project, selecting an environment, and clicking Save. For installations with many (tens or more) tenants, this is quite inconvenient, and has resulted in hacky workarounds from third-parties.

Can we add collapsible panel (like Expand/Collapse) to Project Group. Most of the time I have to scroll down to search my projects, so it would be easy if we add expand collapse section.

We have a dev cluster set up and working with octopus.

One of the hurdles to creating ephemeral/adhoc debug/testing environments at the moment is the fact that we have to go in and manually map those environments in lots of different places.

Ideally, we'd be able to create a resource (e.g. a kubernetes cluster, certificate, etc), that lets us specify that it is a valid resource for ALL environments EXCEPT production.

Allow the json payload used when setting up Subscriptions to be templated in the same way as config.
If you could specify the json with embedded octopus variables you could integrate with many many other tools without the need to add a custom step at the end of each deployment. (eg. MS teams)

The current Octopus.Deployment.Targets variable is only available to the Deployment Changes section. It would be beneficial to expose this information during the deployment too.
The use case in mind is sending emails pre-release that mention the machines that will be deployed to, or in the case of Azure, could expose the URLs, given these work on the convention of <machine-name>.azurewebsites.net

Octopus Cloud is presently limited to three Azure regions (West US 2, West Europe, Australia East).
Strict data sovereignty rules for some customers may mean that Octopus Cloud is currently not a viable solution.

It would be good if more regions were supported by Octopus Cloud - specifically UK West and/or UK South.

Also - how does Octopus handle high availability and fault tolerance if limited to only one region?

Given an JSON settings file which has an array element

e.g. { "Users": [] }

Use Octopus variables to insert into the array rather than just replace values.

e.g.
define Users:0:Username = user
define Users:0:Password = password

Would result in the object getting inserted

{ "Users": [ { "Username: "user", "Password": "password" } ] }

https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7

We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.

When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.

After pushing build information from a TeamCity project that was building some code from SVN (subversion) version control system, I noticed that while the package in octopus did have the commit section filled out as expected, the commits were NOT there when creating a release with that package. This meant that we couldn't automatically generate the release notes based on commit messages. I contacted octopus support and we eventually figured out that SVN is not supported.

Whilst in the deployment screen, the 'Deploy' button should be disabled whilst filters are being refreshed and affected tenants loaded.

With the current functionality, it's very easy for a user to add a tag filter and not realise that additional tenants have been included, but are not yet visible in the 'Preview and Customize' section. The loading bar at the top of the box is subtle and easy to miss.

Once affected tenants have been refreshed, the button should be enabled again.

Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
This is not possible now, the only solution now is to cancel all the existing tasks.

It would be helpful to have a description field for variables in a project or in library set variables. I know the idea of having 'descriptive variables' usually solves this issue but sometimes across teams it doesn't always happen.

To save screen space it could be a descriptor you enter when making the variable then when you mouse over the variable it shows the information descriptor.