To restrict a team to a specific project, the Project Groups is supposed to be left EMPTY, even though the PlaceHolder text says "Any Project Group".

A better UI design would be to have a box of Projects/Groups, where the autocomplete will include both groups (as "ProjectGroup*" or "ProjectGroup - All Projects") and individual projects (as "ProjectGroup\ProjectName").

In using this UI, a multi selection of GroupA* + GroupB\Proj1 is as obvious as GroupA* + GroupA\Proj2 (which would be obviously unnecessary and redundant)

We'd love it if the Octopus Server could authenticate with its underlying Azure SQL database via Azure Active Directory Integration Authentication instead of SQL Authentication. Our Octopus service runs as an AD service account that is federated to our Azure Active Directory, but I'm still forced to use SQL Authentication at the moment.

https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication-configure

Select multiple deployments for comparing variables used.

Add a documentation field in the variables view: a column for "category", or "comments" (informational only). It would be nice to be able to see that a variable is for transforms, or is data that is passed on to an external application, etc, without having to dig through the process. This can be done to some extent with variable names. However, I don't want to be changing variable names down the road just to clarify their usage.

While it should be possible to configure nginx/haproxy/etc to act as a transparent reverse proxy, it is a commonly accepted convention to use the X-Forwarded-Host and X-Forwarded-Proto to pass the original requested url to the proxied application.

It would be nice to support these headers.

I'd like to be able to setup a project to never cache the steps that were in place when a release was created. Or at least have a way to update that cache the same way you can update to the latest variable set.

When we update the deployment steps now we have two options:
1) Rebuild from source (which we should never have to do)
2) Delete and re-add the release (which loses any deployment history)

Now that we are starting to embrace channels, we are finding that we want to limit which channels can go to which stage in a lifecycle. For instance, we have two channels - master and pull-requests. Pull Request (aka deployment per PR) can only go to the Staging Environment, but the master channel can go to Staging and Production.

Right now we have two life cycles to make this happen, but that causes a lot of extra life cycles.

The dashboards show each of the environments to deploy to, but they don't indicate which are part of each individual phase of a lifecycle. This means if we need to deploy to one of five environments it can get a little confusing without a really clear environment name.

I propose that we draw a line divider in between the phases or colour the environments within a phase differently from each other.

Is it possible to create an AWS AMI using Hashicorp Packer with Octopus server installed? Is there any guidance or documentation? We're finding it a bit difficult.

Keyboard navigation isn't always usable in the web UI of octopus deploy. I find myself hitting ctrl-s regularly expecting that things are saved, ctrl-c or specs to leave a pop-up without saving etc.

These Cmdlets are a HUGE timesaver since you can't (as far as I know) create a copy/clone of a variable set.
The module does a lot more though, however the latest binary from 2015 doesn't work anymore and the developer doesn't appear to be keeping the code up to date.

When working with a number of library variables, sometimes we don't name them as well as we should. Inevitably, we look at a variable and say "where is this used again? Client side transforms? A step template?" -- If Octopus was able to report which variables were used where, it could help us better remove unused variables, and help us better organize the existing ones.

We are running multiple services, each with their own IP, on the same windows server and it would be extremely helpful if we could bind the Octopus server to a specific IP. As it is now it is not certain that it will use the IP we intended it to use, which might also affect the other services.

A simple IP choice in the binding interface would be great.

The powershell editor is great, but:

I know that there is a "full screen" button, but would it be nice, that the default editor adapts in width and height to the actual viewport?

or make it at least a little bigger, it loks ridicoulous small on my screen.

And there is another issue with the full screen size: the "insert variable" button is hidden (why?)...

Often times various components that make up a 'whole' project can exist at different version numbers. A WebApi project perhaps, a UI project, a SQL Database project. The three of these things together comprise a single solution. It would be nice to have component based projects (as currently implemented) and then to have a sort of parent/solution container.. so that for the container, I can click a button and bam, all sub-projects get deployed.. or, if I want, I just click a button and release individual pieces of that whole project.

We have lots of machines/tentacles with lots of different roles. It would be helpful if we could search all projects that use a given role. This would show us all Octopus projects that are assigned to a given role.

Adding or removing roles from clusters of servers that are 30+ servers is a pain to do one by one. it simply takes forever.

It would be fantastic if I could mark all the servers that I need to manipulate roles on have one dialog box open. Add and/or remove the roles I need to change. When pressing OK my job is done: I've successfully added the 'awesome' role to 30 servers in less than 1 minutes.

Also this would make my management work less error prone as today I might have missed a server or two in the process.

if you deploy a nuget you have various options to change config or other files with transformation and replacings.

In the UI the Order is

Configuration variables
Configuration transforms
Substitute variables in files

But in the Process executing it is

Substitute variables in files
Configuration transformation
Configuration variables

please change to UI to reflect the process.

Customer has requested we add some basic IP level restrictions to the Cloud instances when accessing via VPNs or other restricted networks