Currently it is necessary to page back through the releases list to find one by release number.

Using a text filter rather than specific version search would enable e.g. SemVer release prefixes to be searched/targeted.

Via @readyroll

Perhaps we should just implement a global search?

If I create a new machine with a new IIS, it comes with a 'default' website.
Now of course, no one uses that default website, so I would like it completely removed if present.

So, I would like an option to have that done. If not, it likely creates binding issues when the actual site is deployed.

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

If I have a variable set like:

| ClientEndpoint | http://#{ClientAppName} |

...and I include it in a project that doesn't define ClientAppName I'll get a prompt like:

"Hey, you've included a variable set that depends on a number of variables, which aren't currently defined. For example: ClientAppName, ..... Would you like to add these to your project variables?"

Providing a checklist to exclude any that might be coming from elsewhere seems like a necessary UX requirement.

When setting up vpn access for a deployment, it can cause issues if multiple users attempt to setup access concurrently. One way to stop this would be the user checking if any deployments are currently going on, but users don't always have access to other projects.

It would be nice if there were rules setup to limit the number of concurrent deployments, or even just limit certain deployments so that they cannot run concurrently, adding it to a queue.

I've setup global libraries. One is named Global which defines settings (across all environments) while i have other libraries named Dev, QA, Staging, and Prod. I'd like to be able to allow QA users have access to only edit the QA library similarly how they currently can only deploy to QA environments. They would be able
to define new variables that override the global variables for their environments to validate their testing needs.

It would be awesome if the favicon could change in some way to reflect the status, this enables me to browse other sites and still keep in view the in-progress, success, fail status of a deployment.

When on the dashboard it could reflect an aggregate status.
When on a Project page the favicon chould reflect that project (or both project and aggregate status)

example: https://status.github.com/

Would be cool to be able to upload documents (e.g. test reports, approvals etc) to a manual build step and have these stored against a release for traceability and audit purposes.

The current readonly roles do not let a user to see the detailed output of deployments.

In larger enterprises, the dev teams can't deploy to production. However, they need to be able to see the output.

It would be nice to be able to restrict deployments to certain environments ( for instance the production environment) from being able to happen on certain days/times. IE only at weekends or only after 8pm

At the moment I use a powershell script which just throws an exception which stops the deployment but it would be nice to have this built in. Especially if it could be linked with the "Schedule a Deployment" idea. Then if someone tried to deploy it could say unable to deploy at this time do you want to schedule for the next available time.

When collapsing a log entry/header for a task it would be great if the total duration was displayed. That way it would be easy to spot slow tasks in a full deployment.

I have different applications that deploy to different sets of servers. I could create unique environments to handle the separation but it could get ugly pretty quick. If a project group was tied to a set of environments it would make it easier to know what environments apply to that project and prevent me from selecting the wrong environment to deploy to.

Enable double click or something like that on a Tentacle machine in the environment overview. When you click/doubleclick/other then adownload is started with a preconfigured rdp file.
Just like you do on amazon.
This way its easy to open a connection to a specific tentacle and octopus only has to create a downloadable rpd file, with server name and possible pre filled domain/user,
VERY nice feature for handling your servers and apps :)

I really like the new feature where Octopus can create or modify the IIS web site and application pool. In some cases an administrator may want to change some of the configurations on the web server which shouldn't be changed on the next deploy.

I would like to be able to configure this step so that it will only create the IIS web site and application pool if they don't already exist.

Add support for custom pages or widgets that can be added to the Octopus Server installation along with custom fields that can be assigned to Project and Release. An example would be a NUnit widget that could use API to fetch NUnit test results artifact and format it nicely on release page. Other example could be storing 'build quality' property along each release. The value would be updated e.g. by the build server after executing unit tests or integration tests or a QA person after doing some exploratory testing