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.

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.

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

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?

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.

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.

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

Give an option (or make it default) to have the "Acquire Packages" step to always happen at the very beginning.

Our use case:
We uninstall a program, then extract the package and install it. If it fails on the package download (which happens automatically right before the extraction), then our deployment target had all of its files deleted, but failed the deployment.

Our current fix:
Make sure the "Extract Packages" step is the first thing in every project, to force "Acquire Packages" to be at the very beginning

Fix typo in /opt/octopus/tentacle/configure-tentacle.sh.
Applications is misspelled as "appications".
Found in tentacle-5.0.12-1.x86_64.rpm.

read -p "Where would you like Tentacle to install appications to? ($applicationpath):" inputapplicationpath

read -p "Where would you like Tentacle to install appications to? ($applicationpath):" inputapplicationpath

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.

Could you please consider showing the release notes as a hint box when user would hover the release number in the Project/Deployments/Overview view?

Currently the release number is "clickable", so we can reach the release (and its notes) quickly, anyway there is no hint used, so it would be more comfortable just to point the cursor and read the notes.

Thank you.

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

Please can a view be added that allows a user to see all deployments in a pipeline, spanning all tenants and channels? Having to search for these seperately causes no end of headaches as I often have to line up versions and this is made harder when they have to be searched for. Making it so they are all visible from the main page of a release as an optional view would alleviate this.