Adding a 'clean' function (similar in nature to MSBuild clean) that removes old packages when creating the new one. Especially relevant for when you publish the package to a file share or feed.

Sensitive variables pass to script as a String, so they could be written to file/socket. I think there should be an option to make those variables more secure and pass them as SecureString instead of String.

On a projects Variables screen, once we enter a new variable it stays in order on the screen. I would like the ability to drag and drop each line to a new position. This way I can ensure as I add new vars or update existing ones the ordering of them makes sense (at least to me)

We've started looking into handling container deployments with Pivotal Web Services, it'd be great to add Cloud Foundry support as a deployment option, similar to AWS or Azure.

As of 3.0.11. prompt variables can only be scoped to environments. It would be good to be able to scope them to steps, roles and machines as well.

The FTP deployment step supports FTP and FTPS but not SFTP. Adding this would let Octopus users securely deploy to a much broader range of systems (i.e. Unix-y ones instead of Windows).

It would be great if Octopus would replace values in the smtp (http://msdn.microsoft.com/en-us/library/ms164240(v=vs.110).aspx) element in web.config like it does with connectionStrings and appSettings.

We currently want to set features like the number of worker processes. It would be good to be able to set these up from Octopus instead of powershell.

Native integration with ServiceNow so teams can link releases to change requests and pause deployments to production until approvals are met.

New-OctopusArtifact allows you to attach an artifact to a release. If you wanted to use that same artifact in another step on the same deployment, you'd need to use the API.

It might not be such a bad idea to have a Get-OctopusArtifact cmdlet that returns info about that artifact, as well as a Download() method the download the full file from a Tentacle.

Fully support of Elastic Beanstalk for deploying HA web applications that make use of the built in feature set plus the rich features provided. H octopus.

Offline install packages are a nice way of introducing Octopus and Calimari installs into an existing enterprise without having to directly attempt to change the change management process straight off.

However in doing so one of the principal 'sell' points of Octopus - centralized logging - is lost.

It would be nice if offline installation also took care of transmitting the installation logs back to the central server (presumably if possible), so the installs would look largely like any other install.

I have accidentally deleted projects multiple times now.
When I am in a rush and want to manually recreate a release I have to delete it - which has a very similar sequence of actions required to delete the project! :(
The only way to get the project back is to restore the database. It would be nice if you could just hide the project from the GUI and keep it into a trash can somewhere which could retain it for a limited perioud (e.g. a month).

When working with larger projects that contain steps within steps, the page refreshes often when making changes so this involves a lot of scrolling to find the steps you are working on. It would be great if you could collapse steps that contain children so there's a smaller list to scroll through.

We miss ability to undeploy a project from servers.

Undeployment could run an Undeploy.ps1 script from the package that would contain logic for removing the service from a server (removing web app files, deleting databases, uninstalling a software).

Currently there is no way to remove a project from a server if it is no longer used to run a service from the project (eg. changing where an web app will run, or removing programs installed by the deployment scripts).

When choosing to try again on a deployment it would be really nice to have an option to skip all steps that did deploy successfully.

When working with large number of project groups and projects, it would be great to have some more control over the project screen UI. E.g. Allow a user to collapse a project group so that it it hides all projects. Allow a user to reorder project groups (as per environments), so that you can place commonly accessed projects where you want them.

https://github.com/OctopusDeploy/Issues/issues/591