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.

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.

Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.

Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.

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.

Octopus does not provide date time filter for any of the Octopus APIs.
Which makes very difficult to pull data for an older date.
There is no way other than loading each page then take the Page.Next value and compare the date.
Its time consuming when the date we search is really old.

I would like Octopus deploy to support the date filter for APIs.

There is one more drawback while using APIs with out date time filter which is explained in this page.
https://help.octopus.com/t/date-filter-for-octopus-apis/25111/3

This was previously asked for and done here https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/3133236-non-javascript-based-links

But we updated from 2019.6.8 to 2019.9.10 and this has broken in at least one spot.

If you click "Project switcher" and search for a Project the dropdown no longer gives links that can be open in a new tab.

This makes me sad. :(

Please provide integration with Azure App Configuration. We need the task to download variables in the process runtime. This will allow to use Azure CMDB and Octopus for deployments.

Octopus supports Terraform-Steps. It uses Terraform 0.11. Terraform 0.12 has been released and has a few breaking changes. Update the Terraform-Integration to be compatible with Terraform 0.11 and 0.12.

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.

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.

The idea is to have the tenant variables displayed vertically, with one column for each environment.
Currently, it is quite tedious to compare or copy variable values from an environment to another.

Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.

We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.

It would be great if you can persist the state of excluded steps to the next environments as part of same release?

As per - https://help.octopus.com/t/deploy-a-release-accessing-variables-from-last-release/22788

You should be able to access a previous releases Step output variables, for when a release has already been deployed.

Either via the Deploy a release step.
Or more generally to retrieve these values for a given release.
E.g. an obtain Release information step

The deploy release step assumes want to deploy to the same environment as the parent deployment.

Add facility to pass a parameter to chose which environment to deploy the release too.
E.g. so can deploy a single master release, which kicks off multiple deployments of other release to the defined environments specified by the parameters.

Similar to how the community Chain step template allows for.

Right now you can view a Team and see what project or project group that team has access to. We'd like to see the reverse as well. When we go to a project or project group we'd like to see the teams that have access along with their permissions.

When i edit a step in deployment process I see left side pane steps starting from 1,2.....etc. i don't see the one I am editing scrolled up.