Currently there are a few feeds that support v3 NuGet feeds. Octopus currently does not support linking directly to the JSON file. Please add votes and feedback on why you would like this supported by the few feeds that currently do.

Please note that this is not about Octopus updating its NuGet library to support things like SemVer 2.0 which is planned. This is strictly when you add an external feed to retrieve external packages.

When working with library variable sets used in many projects with many steps it is cumbersome to figure out where a given variable is used.

When updating a deployment process, certain tasks become very difficult, such as:
-Renaming or deleting a variable
-Checking validity of a newly-updated variable value across all usages

With a "find all" feature these tasks would be much simpler (plus I'm sure there would be wider-reaching benefits).

Currently the automatic release creation feature does not resolve variables when looking if a package is used in a project set for automatic release creation. You can only use package IDs with static names.

It would be great if you could use variables in the package ID and have them resolved when the package is pushed.

Source: http://help.octopusdeploy.com/discussions/problems/28069

I regularly use nested variables to minimise the number of variable changes I must make between environments. Consider something like this:

data source=#{Database.Server};initial catalog=#{Database.Name};#{Database.Auth};

This allows me to just specify simple variables for the DB server, the DB name and the type of auth being used, without having to construct a connectionstring every time (and probably making the odd mistake).

It would be great if I could see the fully-evaluated variables when i click "Show variables" on a release - or at least have a switch between the raw variables and evaluated variables.

It would be great to see Python listed as a script step. Python is heavily utilized in the infrastructure space, AWS, F5, Citrix, VMware and will help to drive full automation further up the stack.

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

It'd be awesome if clicking on a Project Group in the Projects drop down took you to a dashboard that ONLY listed the projects under that group.

Better if an admin user can still hide/show projects in those virtual dashboard for everyone

Even better if each user could configure a custom version of that dashboard for themselves

Would like that OD is in compliance with the latest version of SemVer, so that the Pre-Release flag, and Build Metadata can be utilized in the release number.

In some environments we do not want a Windows Service started after it is deployed. In the current Octopus.Features.WindowsService_BeforePostDeploy.ps1 file the service is always started. It would be great to have a flag that could prevent the service from being started.

It would be nice to be able to set random values in the config files using an XmlPoke type feature where you could specify XPath expressions that point to values in the config file and then specify values to set them to.

Here is an example to set the compilation debug to false:

XPath: configuration/system.web/compilation/@debug
Value: false

This would allow setting random values throughout the config file without having to use config transforms.

We have multiple projects being deployed to different servers in heterogeneous environments. Some are just test-production, others are dev-test-staging-production. The projects often have completely separate environments.

It would be beneficial to be able to either choose which environments a project can deploy to, or to be able to set up per-project environments to be able to keep the same names for config transforms. (ex. "Web.Test.cfg" instead of "Web.Test-Product1.cfg")

Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects.

In our project we have 2 branches - trunk and patch - both of which produce packages for Octopus and use semantic versioning when creating the Octopus release in the build. I would like to specify a build from the patch branch explicitly so that when packaging off the trunk my release would be 1.24.102948 but when packaging off the patch branch my release would be 1.24.102949+patch. My workaround is to use the pre-release metadata so my patch builds are producing octopus releases 1.24.102949-patch.

A flag on the Email template step to send the email as High Priority. We use the Email template step (when any step fails) to notify that the deployment failed and it would be more convenient if we could set the flag for high priority. I could create my own powershell step, but I thought the out of the box email template step could use this feature.

We have "major deployments". At this time we have to deploy all our applications (~ 70) at once. So it would be nice to have a possibility to deploy all projects from environment-1 to environment-2

Current configuration (v4.0+) uses dropdown control for Releases list.
Previous implementation had combo box control and it allowed to do a quick search for large releases lists.

Would love to have this feature back since currently it is not possible to do a 'contains' search among differently named releases.

Logging in always takes a few clicks with the Guest/Account question. As a dev I never want to see the guest option. Can there be a way of preventing it showing - perhaps via a cookie such as "Remember this choice"?

When you list the releases for a product you can see the Version and when it was assembled, but not the release notes. We have this connected to the git commit log so we easilly can see what is being deployed. Right now we have to click each item to see this information

Provide an additional option in Configure dashboard to allow selecting project groups instead of just individual projects. This way if an additional project gets added to the group it automatically appears on your dashboard rather than having to look for and add new projects to the filtered list.