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.

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.

Tentacle authentication happens only using .pfx cert, but it should also use the .pem

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

Some of our deployments have lengthy steps that cannot yet be automated. It would be great if markdown files contained with in a package can be used as manual intervention steps in a deployment.

I was thinking this could work by simply having an option to choose a file rather than type the instructions on a manual intervention step.

However it would be really great if some naming standard could be introduced. For example "PreDeploy.md" would appear as a manual intervention at the start of the deployment.

User credentials are the only supported method of authentication with Service Fabric and AAD. Client application credentials are not yet supported. It would be great to use the actual AAD Application to authenticate.

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.

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}

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

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.

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.

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.

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.

Given the Octopus Projects are not source controlled, comparing projects is quite difficult, so I resort to Export process and export variables to json and then do a file compare.

This is made difficult when comparing variables, as the json file is in no particular order. It seems the most recently edited variable is at the bottom.

Can we please arrange the variable in a set order, perhaps the same as the UI.

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.