Currently it looks like Octopus uses the userPrincipalName when syncing/authenticating users from AD. Since the UPN may change (for instance when migrating users to Office365....), users will suddenly end up with a new account in Octopus when loggin in using Windows Auth.

Using the samAccountName (as is more common) should allow users to keep their Octopus account/profile in situations like this.

As an IT compliance officer I need to be able to view the Audit page in Octopus Deploy but I don’t want to be able to make changes to the Octopus System. Please create an “Audit Viewer” role that has appropriate access to the Audit page separate from AdministerSystem

Please add a a comments field beside each variable. There are times when an explanation would be extremely valuable.

It would be nice if there was a way to expand the roles for a team on a per environment basis. For example I'd like I'd like for the developer team to be able to create and edit variables in the production scope, but not be able to deploy there.

As of Octopus 3.3, the 2 options are:

• 2.0 (for .Net 2.0 and 3.5)


• 4.0 (for .Net 4.0 and 4.5)

It might be useful to also add the option "No Managed Code"

In the project settings there is a "Disable this project" checkbox, when it is checked there should be visual indication in both the Dashboard and in the project header notifying the user of the state.

Offline drops don't currently support passing output variables from a deployment package step to another step as part of the same deployment script. Would it be nice to add them?

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

For every process run on SSH, Mono is required on the end target machine as we rely on Calamari for each process. With our recent extensions into other package types, and script types, removing this dependency would give a much larger range of targets and uses. It would allow for greater scripting.

Adding this suggestion to find from the community how useful this would be - please add comments below about your potential use / server config or really anything relevant to why this is important for you.

We have a lot of projects 50+ and a lot of hosts 200+ so it's a problem with the big icons (they got even bigger in 3.0)
hard to get an overview.
so make a drop-down where we can select Icon or Detail view (like in the explorer)
Atm there is a lot of mouse wheel scrolling happening to get to the host in the end of the list.

We have an environment where there are a mixture of employees / vendors who need different levels of access to different resources in Octopus. No problem. However, I've got a mixture, some who have just local accounts in our Gitlab & Octopus environment, and those who have AD accounts because they use Gitlab, Octopus & other resources in our environment. If it were possible select whether an Octopus user authenticates off of AD or local, that would be MOST EXCELLENT!

Many parts of the internet infrastructure use timestamps, but when Octopus extract files from NuGet packages the original timestamps are overwritten with the time of extraction. This causes pain with load-balancers, edge caching, file sync...

It would be very (very very) nice if Octopus would maintain the original timestamp from the original file upon extraction.

Source: http://octopus-deploy.tenderapp.com/discussions/problems/17537-timestamp-not-preserved-when-tentacle-unpacks-packages

Source: https://github.com/OctopusDeploy/Issues/issues/829

Source: http://help.octopusdeploy.com/discussions/questions/6829-is-it-possible-for-octoexe-or-octopack-to-maintain-last-changed-dates

Please support deployments of the new Azure Service Fabric "microservice" architecture platform.

See http://azure.microsoft.com/en-us/documentation/articles/service-fabric-overview/ for the initial documentation and Channel9 build videos.

For Packages I can define a retention policy. However I observe the disk space usage keeps increasing and runs out of space once in a while. The reason is that the PackageCache with .octosig and .octodelta files never gets cleaned up. It would be nice if the retention policy could maintain an acceptable size for the PackageCache as well.

I want a GUI that can answer the question of how many tentacles/deployment targets do we have and what's the health status for them.

Improve Amazon Web Services integration by adding built in support for AWS.

Example: give your AWS credentials to Octopus and him will create automatically an instance with a Octopus tentacle installed on it.

We currently are writing many powershell scripts to work with octopus deploy as part of our deployment and then having to keep a copy in our github repo to be used by the devteam. I'd like a way for octopus to have access to the repository and notice there are changes and allow for a manual update, as it currently works.