The search is case sensitive when searching for a script module in the "Include a Script Module" dialog from the Process page.

I think this should be case insensitive.

The Set-OctopusVariable (and its counterparts for other scripting languages) should support an -IsSensitive flag such that if a variable is marked as sensitive it will not leak into a log.

I would love to see built-in support for Terraform (https://www.terraform.io/). Deployment steps for each Terraform operation like "plan" and "apply" and also a Terraform backend plugin for storing state.

Ideally variables can be read without expanding the browser to both windows - probably a bug

Screens:
https://ufile.io/nf3ps

The new Docker features debuting in recent versions of Octopus are really promising, and I'm excited by the Docker Compose RFC published late last year.

Kubernetes is becoming increasingly popular as the production deployment environment of choice for containerised applications. It offers functionality very similar to Azure Service Fabric, in terms of auto-scaling and self-healing of services and applications, but is based around container images rather than zip files.

Allow Octopus to download from Maven repositories servers instead of the Build-in Octopus repository.

I just updated to the new 4.0.3 version of Octopus. I do NOT like the process to skip deployment steps. It is hard to follow and see what is going on and takes way longer than the older versions. Please change this to something more like the older version where I can see all the steps and easily click on the ones I want to skip.

One of the people on my team couldn't even figure out how to skip the steps it was such a pain to find.

Excluding steps has become unmanageable, please revert to what you had before... causing us hell.

Right now only manual intervention steps cannot be skipped during a custom deployment. It maybe good to be able to mark any step as unskippable.

in our Deployment processe we have 25 steps.
on old version we was able to check or uncheck for example steps 1 to 10. in order to deploy first part or second part.

but now in the new version the exclude steps is not as esay. you have to open select box, select one step. the selectbox is closed. then you have to open it again and select the next step... 10 times... it is lot longer thant only chech on uncheck visible checkboxes.

i would expected an easier way but now it is an harder way...

The users view that pages user into n number of pages, makes it a hassle to find a user when you have 100 or more users.

I would like to be able to search for a user, and search across username, displayname and email address.

As it is now if you can change the deployment process, you can also set scripts to run on the Octopus Server. We want people to be able to change the deployment process, but not to run scripts on the Octopus Server. A permission or feature-toggle to restrict that option would be great.

we do not see anymore the comment on the release list.
it was helpful to have a small remiinder of difference between versions

While typing in the value of a sensitive variable, the complete value is always visible while typing it in.

It would be more secure if there is an option to obfuscate the value while typing it in.

octo.exe is a great tool that wraps much of the Octopus Deploy API. It would be great if we could specify a parameter --output-format=json or --output-format=xml to have octo.exe generate its results in a machine-readable format for further scripting (e.g. in an environment where I have an older version of Powershell without access to modules such as Octoposh).

It would be nice to be able to add notes or an alert to tenants so that we have some warning about release windows or contact people against a tenant.

Allow C# and F# scripts to include references to NuGet packages that are downloaded and referenced before the script is run (see http://scriptcs.net/).

Preferably the feed could be any defined feed and not just NuGet.org.