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

Octopus Manager and Tentacle Manager should make it easy to configure the Windows Service to run under a custom user account.

Allow tagging environments with keywords to group similar environments together. Then use these environment tags on the variables page to scope variables to groups of environments without needing to specify each environment separately.

For example, we have US and Canada dev, QA and prod environments. It would be nice to tag the US dev, QA and prod environments with the "US" keyword and the Canada dev, QA and prod environments with the "Canada" keyword.

It would be nice if the HTTPS binding feature allowed you to use the IIS 8 Centralized Certificate feature instead of requiring a Thumbprint and locally installed certificate.

http://blogs.msdn.com/b/kaushal/archive/2012/10/11/central-certificate-store-ccs-with-iis-8-windows-server-2012.aspx

The .net SessionState provider uses the IIS site ID as part of the key used to access a session when working in out of process mode. If you are running a site in a webfarm these ID's need to be kept in sync with each other otherwise as requests bounce around the servers a different session will be accessed.

It's probably not a big issue as more complex set up's will probably be using custom set up scripts but I think it'd be a very easy feature to add.

Make it possible to manually resize the insert variable panel.

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

Because a lot a Octopus variable names has long characters, I can't see the entire name of almost of variables in the 'insert variable' panel. Is it possible to allow to grow the panel manually? Or provide a fullscreen mode will be a good idea.

http://octopus-deploy.tenderapp.com/discussions/problems/18000-project-specific-nuget-feed

TC exposes artifacts to users that has access to the project that has generated the artifact. In order for our OD to be able to pull packages from a TeamCity nuget feed the configuration must supply credentials to TC.

With nuget feed configuration being global there is no way I can prevent one project from accessing the artifacts from another project.

In addition to the global set of shared nuget feeds, each project should have its own set of private feeds.

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

Would you consider supporting net.tcp binding as an IIS Binding type so that we can configure WCF services via the "IIS web site and application pool" feature. Currently only HTTP and HTTPS are supported.

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

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

When setting up a user in a team you can currently set Projects and Environments on the team, but if I setup a team as "Project Deployer" they do also get view access for all environments and machines, though they cannot do anything more then viewing.

I would very much appreciate if you could add in a "Roles" field as well in the team setup, so that the users in the team only can see the Environments (Machines) with the same Role.
As default (If no Roles are specified) all Environments (Machines) should be visible.

On the dashboard, when OD detects there is a new version available on the nuget feeds, a small + symbol should appear next to the project name, clicking this should take you to the create release screen.

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

It would be nice to be able to specify if tentacle upgrades should be downloaded from the octopus server, or from the official octopus site.

Upgrading a bunch of tentacles at remote locations at once can hammer a single ADSL connection, though I'd assume the Octopus servers would be better set up to serve the upgrades, especially if they're on a CDN or similar.

Make it possible to generate documentation (HTML or Word perhaps?) based on the current configuration. This might be:

• All deployment steps
• All environments and machines

The documentation should be readable, i.e., here's what's going to happen rather than a JSON dump. Imagine a document you could give to a sysadmin to follow to perform the deployment manually.

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

Sometimes tools that do expensive things will generate a list of this is what I would do if. Would be similar to the deploy button, but would validate variables in powershell, and would show what the expressions would be if it did run.

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

The page should remember:

• Whether you like to look at the summary or output
• Which expansion option you are using

And default to it

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

When displaying snapshots, show any variables whose scope values don't appear in the current set available to the project (owner)

At the start of deployment, warn if scope values have changed (e.g. if Production is deleted and recreated, there will be a variable scoped to the old Production environment ID, apparently useful but not applied)

Where the name associated with a scope value has changed, show the old and new names

If I have a WCF endpoint in my .config file, and an Octopus variable with a name that matches the name of my contract, auto-replace it (just like appSettings/connectionStrings replacement).

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

Current project names must be globally unique. Change the rule to make it possible to have projects with the same name in different project groups, but not in the same group.

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