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.

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.

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

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})}

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.

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" ?

The chrome autofill gets in the way of dropdowns/multi-selects. There is not the ability for a user to disable autofill for specific websites, but this is supposed to work on the developer side:

https://stackoverflow.com/questions/40200130/how-to-disable-chrome-to-autofill-username-email-password/40200269#40200269

Currently, in order to allow developers to access and edit variables, they are also able to edit process steps including disabling them. This means that they are able to disable audit steps before deploying.

If process edit was a separate permission we could split out the ability to edit variables and the ability to edit/change process steps

"Use the version number from an included package" isn't as useful as it could be because whenever I modify a deployment process and go to create a new release, Octopus complains the release version already exists. So I either have to delete the old release or append ".i" to the version number. I would estimate I've appended ".i" about ten thousand times over the years. Would be nice to not have to do this.

Basically this:
https://help.octopus.com/t/how-to-create-a-release-version-with-package-number-and-an-incremental-number-with-it/23869

We use Venafi (https://www.venafi.com/platform/trust-authority) to issue and manager certificates. It would be great if Octopus could integrate with this system to allow for issuance, import and storage of new certificates for the sites we deploy.

The Run page when Running a Runbook Snapshot always has a "Something has changed since this runbook-snapshot was taken" warning. However, the warning might only be about the audit trail of the Runbook Process. Won't the audit trail change with every run? If so, I think this warning is a false positive.

Deployment trigger options are currently limited. It would be nice to trigger a deployment by executing Azure Function which would queue the request using Azure Service Bus. In this case Octopus Deploy would listen for a queue message to start a deployment.

This solution would allow for various creative integrations within Azure.

Just upgraded to 2019.1 - the Spaces navigation item bothers me a lot. We only have one space, and don’t want more spaces (and won’t upgrade our license), yet I can’t seem to find an option to remove this. Something to add under Configuration > Features?