Being able to set the maximum projects settings for the Dashboard configuration on a global level would benefit our setup due to the high count of projects in our Octopus instances.

Most developers have configured their dashboards for their own projects/project groups but a new user, or a user who hasn't configured their dashboard, will experience long loads times on the Dashboard view so I feel that being able to configure that setting at a Global level (reduce the default setting of 200) would reduce the load time for those users and give them a better initial experience on Octopus.

This is a pretty trivial idea, but I like me some logos.
I suggest on the settings screen when you pick a logo, that octopus could automatically do what I do manually.. and that is look up the twitter account that matches my project and the facebook account and... and show the logo/avatar of each, and let me pick one of those. (perhaps give the option to put a different name since sometimes the obvious name isn't the correct one)

We have a project existing out of 60 packages.
In every package the in a appsetting in the config file.
We now need to have in 1 specific package another value for the appsetting.
Now we need to create a new appsetting in the config file and do some coding to read another appsetting for that 1 specific package.
If it would be possible to scope a variable to a spefic step/package would be nice.

On the deploy release page (the one that shows just before actually deploying a release) the channel (if any) is not shown anywhere on the page. Would be very useful to avoid mistakes when deploying.

When a Deployment is canceled, deployment task lists should show as canceled if they did not complete

Currently, when a multi-step deployment is canceled, the machine shows as successful even if only 1 step is completed

On the deployment steps, when a step fails the step entry color flips to red. For a success it is Green

For a person that is Red/Green color blind telling the difference can be almost impossible to detect

changing the step icon from the Plus to a X or Check will make it easier to distinguish

It would be useful to be able to run a deployment in "Debug Mode", where it would execute one step at a time, pausing after each step, so a developer can verify that it is operating correctly.

It would be configurable and we could leverage the existing functionality of how the Health Check steps take targets out of the list for future steps.

It wouldbe nice to display the "Display Name" for an account instead of the username in the audit (I know this can be changed, but if name changes are also audited, it should plug the hole), or maybe both, for PIV logins where the username cannot be changed, or maybe better yet, allow us to tie accounts together or associate them as one.

Proposed by a user here: https://secure.helpscout.net/conversation/246264030/9467 (private link)

As an auditor, it would be nice to see who is logged in and who has logged in from the audit screen.

Octo.exe returns:

• 0 When the deployment succeeded
• 0 When the deployment suceeded with warnings (SWW)
• 1 when the deployment fails

Would it be useful to add a specific error code for SWW? Build servers also have a "SWW" status and Octo.exe could pass this specific error code to let the user know that there was a warning during the deployment.

There are time where Octopus admins want to make sure that all the projects on their instance run a specific step at the beginning/end of all of their deployments. This has been asked a few times already, most of the times by big companies with lots of projects.

Users: Would this feature be useful to you? Please tell us a bit more about your scenario and how would this solve your needs.

Microsoft has just released the Azure in-VM metadata service that will let you know when a machine is going to be rebooted.

it would be great to tie this into the node maintenance functionality so that the node is automatically drained.

It might be useful to do this for AWS as well (similar to https://github.com/scopely/shudder), but that looks a lot harder.

http://help.octopusdeploy.com/discussions/problems/26062

Enable a way to make a changes (add/remove environment, add/remove role) to multiple tentacles at once.

Over time, older releases that are no longer in use just crowd up the release screen. I want to retain their history, so do not want to delete them.

It would be nice to be able to hide releases.

We need permissions around Step Templates. These need to be for: creating, importing, exporting, deleting.

We would like to have the best uptime in our production environment, so we use rolling deployment. In QAT, though, we don't care about uptime. It would be nice to have the rolling deployment option be chosen based on environment