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.

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?

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.

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. :(

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.

It would be useful to notify either all users, a team, an individual of some changes (step template to be deprecated, upgrade occuring) via a toast/message on login so that important messages related to Octopus/deployments are delivered via Octopus directly to the users that need to know.

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

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.

A dotnet core version has been build. I would be great if this was compiled to a linux-arm runtime.

https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle

Delete previous install files when new install (with an artifact) occurs (offline targets). These deletion should keep in mind the configured retention policy in the corresponding lifecycle

Add the ability to encrypt variable strings using something similar to the variable filters.

Something like: #{VariableToEncrypt | Encrypt(#{CertificateVariable})}

When you configure a "Run a Script" deployment step, you can reference a package, and add the "Substitute Variables in Files" feature. Within the help text it says "A newline-separated list of file names to transform, relative to the package contents." which is inaccurate:

For me, using a simple, relative path here e.g. "index.html" didn't work. I needed to use the full extracted path of the package e.g:

{Octopus.Action.Package[EdibleCode.Something].ExtractedPath}\index.html

Also, you can reference multiple packages for a a run a script template, in which case "relative to the package contents" doesn't make sense and needs clarifying.

When iterating through a collection variable using #{each var in array}, it would be helpful to have a sort by pipe
Eg: #{each var in array | orderby var.property}

The octo.exe push-metadata allows to provide package build information, but its format is not documented.

The documentation available at https://octopus.com/docs/octopus-rest-api/octo.exe-command-line/push-metadata states that the "metadata-file" parameter should be a "Octopus Package metadata Json file".

What is the format expected for that "Octopus Package metadata Json file" ?

When steps are executed, right now it will show a green check if success or a red x when a step fails. It would find it helpful to know which steps actually deployed a new package to a deployment target vs. those that didn't do anything because the package was already deployed to the target. This could just be another type of indicator. Right now it just shows success whether it deployed a package or if it already existed. You have to drill and review the logs to determine which path happened.

It would be nice to visually see the Steps that will be deploying a different package than the last one that was in a release. This could be done by just highlighting the row in a different color.

On the face of it, a simple request... add am optional commit comment when saving an edited project. When going through the audit looking at project changes, it would be nice to simply read a project change commit message, when deciphering bit of JSON. It would be optional, so the JSON change is still available.