Now when a step failed you have to set guided failure on in order to retry the step, it would be handy to have a setting where you say always retry failed steps.

For example if you are doing continues deployment where a build server triggers a deployment from a build, you have to:
- login into octopus
- select the correct project
- manually intervene and assign it to you
- retry it

It would be much better if the retry can be done automatically

I think it would be a nice feature to be able to rename roles, there are situation where you might choose the wrong name and at that point if you have many project connected to it it will be annoying to have to update all the projects.

Make it possible to put environments into groups (or rather, to put Tentacles within an environment into groups)

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

It would be great to have the ability to be able to add an approval step for a scheduled deployment, but be able to approve it before the deployment starts.

So for example, if I wanted to schedule a deployment to run at 2am, I have the ability to schedule the deployment, but the approval can happen between now and then, but the rest of the steps only run at 2am.

Source: http://help.octopusdeploy.com/discussions/questions/3081

It would be really nice if Octopus Server (and portal) had the ability to be updated the same way as a release can be pushed meaning through and Octopus nuget package. this would make the maintenance easy instead of having to download and rerun installer each time a new Octopus release is created

So sensitive project variables will be referenced from Azure Key Vault instead of being stored in octopus.

https://azure.microsoft.com/en-us/services/key-vault

3357461 - 'Azure Resource Manager Key Vault support' was only about ARM template Key Vault support.
17973586 - 'Integrate Octopus deploy with secrets managment system Vault' is similar to this issue only for https://www.vaultproject.io

This idea is similar to
https://docs.microsoft.com/en-us/vsts/build-release/concepts/library/variable-groups?view=vsts#link-secrets-from-an-azure-key-vault-as-variables

Currently the new IIS step (introduced in 3.4.7) allows you to create Sites, Apps and Virtual directories, but you always have to deploy a package.

It might be useful for some users to be able to take advantage of the IIS functionalities, without having a deploy a package.

Source: http://help.octopusdeploy.com/discussions/questions/9702

Some of our projects live on shared servers, and run under different users for isolation. It would be good to be able to choose which user a nuget deployment/powershell script runs under so we can protect against mistakes/malicious code in our powershell deployment scripts.

While we can run smoke tests by using the PostDeploy.ps1, such as running nunit.exe or something similar (frisby.js, etc), it would be great to have a way to integrate back into the dashboard (through the rest api?).

Related links:
http://help.octopusdeploy.com/discussions/questions/214-running-smoke-tests-after-deploy
http://help.octopusdeploy.com/discussions/problems/53646

http://jimblogdog.blogspot.co.uk/2012/08/walk-thru-using-wolfpack-to.html

It would be helpful to be able to specify multiple channels for automatic release creation. The way we are using channels, no package is eligible for more than 1 channel. Without this, the development team now needs to remember that for some channels they don't need to go to octopus to create the release and for others they do.

An easy way to attach deployment artifacts would complement this feature very well.

There should be the possibility to create project templates which can be chossen when creating a new project. This should then not only copy everything, but keep the reference to the template. So when something is changed in the template, all projects based on this template should be updated as well.

Steps coming from a template should not be editable in a subproject, but there should be the possibility to disable a specific step in a specific project.
Also there should be the possibility to add other steps between "template steps" to customize the process.

Teamcity has a simillar model.

Add the ability to set the actions to be taken on service failure. This is accomplished via sc as follows:
http://technet.microsoft.com/en-us/library/cc742019.aspx or using Powershell set-service.

At present, we are managing with a custom PowerShell script.

When a release is automatically created from a package push to the private NuGet feed, it would be handy if the release notes from the release was generated from the combination of release notes in each of the packages in the release.

We are more familiar with 24HH format. Thit feature would help europe customers.

It would be great to have ability to select timezone in UI at user or site settings.

I need to implement some form of two factor authentication for Octopus due to regulatory requirements.

A very simple approach might be this: http://www.codeproject.com/Articles/403355/Implementing-Two-Factor-...

Used by Google, Twitter, GitHub etc.

Source: http://help.octopusdeploy.com/discussions/questions/1605

Support deployment of Azure Function projects

When creating a release, allow variable values to be set that will then flow through to all deployments of the release. See: https://github.com/OctopusDeploy/Issues/issues/1149#issuecomment-52598811