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.

Part Two of a 2-part idea.

When we deploy to production we generally would like to, include in the comments all the release notes from all the releases since the last deployed-release to that environment.

But it IS admittedly a bit of a chore.

If Octopus did it, then it wouldn't even be a chore at all and we would continue to love Octopus and feed it plenty of sailors!

<3 u

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.

Recently we have been audited and one of the questions asked of me was to provide a control for how permissions are managed. At the same time provide me with evidence that you periodically review permission changes using a system generated report. This would be very simple to implement using the same audit structure currently used for the deploy process and it would make auditors happy.

In "Run a Helm update" step we need: Enabled Features -> Substitute variables in files

Why?
For example we need to create configMap for our helm-chart. App config locate in this chart, so we need replase all #{values} by values from project scope

Step helm_install:
1. download chart
2. Substitute variables in files (choose location)
3. in custom script (deployment step) create configMap for our pods

If this feature doesn't exist: we need another step where we download app config and substitute variables and use this file to create configMap

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.

I want to be able to say, transform a json file, and then run a script.

Right now the only way to do that is by putting your script into a nuget package, naming it "publish.ps1", using the "Deploy a package" step and targetting it somewhere, then enabling configure features.

We're working on a few Mac minis to be our iOS build servers. We use (among other things) Homebrew as our package manager. For a variety of reasons, we need the Octopus CLI tool installed on these Mac Minis. You guys support MacOs, but it doesn't look like you've added the CLI to Homebrew.

While I was tempted to add it myself, I figured I'd start with suggesting it here.

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.

The search is case sensitive when searching for a script module in the "Include a Script Module" dialog from the Process page.

I think this should be case insensitive.