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

For a given project I often have one IIS binding for my staging environment:

project.testing.something

But the production servers have more

project.com
legacyprojectdomain.com
project.co.uk

It would be great to be able to configure this in a deployment step without having to have separate deployment steps for each environment

See http://help.octopusdeploy.com/discussions/problems/15298-how-can-i-deploy-an-iis-application-to-a-subpath-of-a-web-site. If this feature supported virtual directories, I could use it; but as it is, I must script all of these feature in Powershell.

Of course the NuGet server is easily managed manually through the file system, but it would be nice to have Octopus discard old packages based on some combination of date or last x versions.

The auditing feature is good, but without any filtering tools, it’s too cumbersome to navigate effectively. Can you add filtering options by: User, Date Range, project or team, action type, etc. etc.?

Make it possible to mark a step/action as "disabled" so that it does not get run.

Not sure what the scope should be - should it apply to any release with that step, or just new releases created?

Create a plugin that makes it easy to trigger a deployment in Octopus from Atlassian Bamboo, like the TeamCity plugin.

You can re-use Variable Sets into multiple projects, which is great.
However when you go to visit your projects Variables page, it just says a Variable set is Included. You get no real information (or link) on which variables are included in that variable set.
It would provide a better overview if the Variables page also listed the variables in the Variable sets. (read-only)

Any possibility of enabling us to specify a regex to filter the nuget packages when on screen after clicking "create release"?

We have multiple branches of the code being worked on at the same time. Each branch has a different major and or minor number.
Ideally we would like to be able to filter accordingly so that we see the latest matching a regular experssion or major / minor version.

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

We need a better view for the variables in a project, once you have a few variables it becomes difficult to make head or tail of the variables list. Particularly when you start to have variables with the same name but different values dependent on scope (i.e. environment)

We should be able to group the list by scope or name

Please update the documentation around artifacts. It is very hard to find how they work.
I know there is a small part in here:
http://docs.octopusdeploy.com/display/OD/Script+Console#ScriptConsole-Collectingartifacts

1. Update this page with details or a link to the Artifacts section:
   http://docs.octopusdeploy.com/display/OD/PowerShell+scripts
   This is where I'd need it most not in the script console which feels more of an ad-hoc type of running stuff on the servers.




2. On the Task Summary page there is an "Artifacts" area (top-right). Add a link from there to the help page from 1 about what artifacts are and how can they be captured.

When viewing a NuGet package, it would be nice to expand and see what is inside it (perhaps just for the built-in repository or repositories on a file share):

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

Create a plugin that makes it easy to trigger a deployment in Octopus from Jenkins, like the existing TeamCity plugin.

It would be useful to be able to get an email notification if any of my machines fail a health check.

We have some steps containing powershell scripts for e.g. deploying proxies, getting instances in and out of load balancers, running smoke tests etc. that are fully parameterized (relying on variables in the deploy project).

In order to keep it DRY it would be very useful to have a library of these step "templates" that could be referered from different deploy processes. Of course they would need different targets/roles, but other than that all that differs is the variables of the individual deploy projects.

Octopus 1.x allowed for integrated Active Directory authentication such that the user didn't have to logon again to access the website or even the api.

It would be very helpful to allow this to continue to occur in Octopus 2.0 as well so that the users don't have to continue to enter their credentials repeatedly.

Some corporate security policies do not allow for 'Remember Me' functionality to be used.

Would be nice if the the web site would work with my ASUS TF701T Android Jelly Bean tablet so that I can watch octopus videos and read documentation. The menus don't work on Android for some reason.