Would be nice to have exclude filters. At the moment, we have a deployment hook based on deployment events and it fills up our Tasks section. It would be nice to be able to exclude certain items so we can reduce the noise when searching for important information.

It would be nice to be able to see how much space packages are taking up for an Octopus Cloud instance and whether you are reaching the max amount allowed. The maximum space allowed in Octopus Cloud is not documented I believe.

It might be helpful to have this knowledge so we know when to use Octopus Cloud's built-in repository to host packages versus utilizing an external package feed from elsewhere.

We are able to manually download the certificates from octopus certificate store, it will be helpful to do the same in build step as sometimes we need to copy certificate files to the application servers.

It's a hassle to scroll to exclude steps during a deployment particularly when your debugging a deployment and don't want to/can't disable steps.

Add the ability in the variable editor to set a variable value to only be used during a specific date range. Dates should be able to exclude year. "Every Oct, Nov, Dec" for example.

In multi-tenant implementations, the Tenants screen only shows 30 tenants. When the left side list of Tenant types, upgrade rings, hostings, etc, exceeds the height of the list of tenants, the "Load More and Load All" button/link is pushed to the bottom of the page and requires a user to scroll to see there are more tenants to choose from. This has caused us to miss several tenants when making configuration changes because it looks like we are seeing all tenants on the screen.

I have a screen shot but I don't know how to submit it.

We want to standardize on some templates that all developers can use for their deployments. That because we need to add compliance checks on all code before promoting to Production.
the 'Run custom script' built-in step is dangerous because that opens the opportunity to do more or less anything.

As an Octopus admin I want to disable some of the built in step templates.

Like many others, we use Terraform to manage our cloud infrastructure and it would be great if we could create and manage our octopus setup in it too.

This is a follow up to the question posted on the Octopus Help section: https://help.octopus.com/t/any-plans-for-an-octopus-terraform-provider/20853

It would be nice to filter subscriptions by project group. We have hundreds of projects and I wanted to subscribe to a subset but even that would require a lot of time to pick an choose projects. in addition, as we add new projects, we would need to update the subscription. if we could filter by project group, then any projects in that group would automatically get a subscription.

It would be very helpful to have a way to collapse the variables by environment when on a Tenant's Project Variables screen. Currently it shows all of them at once, but we have 10-20 variables for each one, so even having a tenant with two environments can quickly become overwhelming and difficult to scroll through. A simple toggle at the end of the environment bar to collapse them would greatly speed up our interactions with the screen.

Please add support to connect to Azure Stack to Deploy VMs, Appservices ...etc

Add repository retention feature for external feeds. I'd like to be able to manage package retention on external feeds in the same way that they are managed for the internal feed automatically deleting unreleased packages after a number of days

The new GitHub Repository Feed Type looks very nice! It would be really great to see the same of functionality with GitLab.

With an increased release cadence, it would be nice of Octopus supported the idea of creating freeze/blackout calendars that would either (by setting) outright prevent deployments (possibly allowing with authorization by a particular team) or display a warning that the deployment is taking place during a freeze period.

Ideally we would be able to associate these freeze calendars with projects or project groups, specify whether it is a warning when deploying or prevents deployment, and in the latter case which team or teams would be able to authorize bypassing the freeze.

It would be very useful to be able to Clone a Channel.

Add a deployment feature to the Azure Web App step that maps Azure's AppSettings and Connection Strings to Octopus variables. It was suggested to use a script to do this on your blog post (https://octopus.com/blog/azure-functions), but this would be much more valuable as a built-in feature since it is such a common scenario.

I've uploaded an example image of what I imagine the UI would look like to: https://imgur.com/a/BwL4Tuh

Currently, the Scheduled Triggers option allows setting a time to deploy, and even includes examples in the documentation for "nightly deployments." The downside currently is that it will re-deploy every single night, even if the environment was already successfully deployed to.

It would be nice to add an option to only deploy if the environment / targets need it done. This would allow for a real nightly promotion without excess deployments and logs.

There seems to be no way of comparing variables between releases. Having this feature would give confidence that only expected variable changes make it into a release