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

Octopus Manager and Tentacle Manager should make it easy to configure the Windows Service to run under a custom user account.

Have an entry field that accepts the same sort of content as is seen in the transform window here: https://webconfigtransformationtester.apphb.com
as well as maybe a file pattern/name to match the transformation to.

This way one can avoid building multiple instances of an application, one for each build configuration (environment), transforms don't happen at build time and can take place as part of a deployment.

I would be really cool if there was a deployment step for AppHarbor.

AppHarbor has a build API that will let you pass the SHA you want built.

Not sure how to best implement it, but having Octo control my AppHarbor
deploys would def be nice.

Source: UserVoice Support Ticket 281

Create an Octopus variable that contains the last installed directory paths for the steps in the project. This becomes useful if you have one step that deploys and another that works on the previously deployed step, but for some reason you deployed one set of steps first and later the remaining steps.

If I want to edit a project group, I must first navigate to the "all projects" overview page. Would be nice to just have an edit icon in the "Projects" dropdown for easier access.

On the process tab it would be really great to already there see if a step needs to be updated because the underlying script has changed.

Also it really simplifies the configuration work if its possible to just click a button "Update all steps" which does exactly that..

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

Today if I select to have the instance count use the count from the Azure management portal and an instance isn't pushed yet (if I had deleted it for example) then it will fail and I have to go in an set it to the value from the config file and then switch back to use Azure mgmt. I'd prefer that it would fallback to the config file if it's not deployed in Azure yet.

For PowerShell scripts it would be good to know the deployment start time.

This way later scripts can report how long a deployment took up to that point.

(A current workaround is to have a script run at the start that sets a variable for later use by other steps)

We use Project Groups to categorize our projects, but a lot of them have very similar names. When looking at Teams, as an example, the project selection only shows the project name without any grouping. When the project list is large, it gets difficult to make sure the correct one is selected. It would be nice if the group was included to help organize the projects, the way the main project menu works. The same thing would also be helpful in the breadcrumbs when navigating inside a project and really everywhere the project is displayed or selected.

Make it possible to manually resize the insert variable panel.

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

Because a lot a Octopus variable names has long characters, I can't see the entire name of almost of variables in the 'insert variable' panel. Is it possible to allow to grow the panel manually? Or provide a fullscreen mode will be a good idea.

Hello

I find it important to check the actual contents of the folder i am deploying to, in order to be sure that everything worked as expected.
Wouldn't it be great to have an embed file manager to see the folders and the files of the server you are deploying to?
Every server, every environment, every project, with user management, and permissions...

this would come in handy, even without deploying something really, just checking files, altering something in servers, without having to remote desktop, or use ftp etc. All centralized.

thanks

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

It would be nice to be able to specify if tentacle upgrades should be downloaded from the octopus server, or from the official octopus site.

Upgrading a bunch of tentacles at remote locations at once can hammer a single ADSL connection, though I'd assume the Octopus servers would be better set up to serve the upgrades, especially if they're on a CDN or similar.

Make it possible to generate documentation (HTML or Word perhaps?) based on the current configuration. This might be:

• All deployment steps
• All environments and machines

The documentation should be readable, i.e., here's what's going to happen rather than a JSON dump. Imagine a document you could give to a sysadmin to follow to perform the deployment manually.

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 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.

The Variables section a Release page appears to show all variable that apply to the release, would it be possible for any variables which are obviously being overwritten to be omitted from this list?

As an example, if I have a variable in a Library which is being overwritten by this particular project, at the moment both will appear in this list.

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

Current project names must be globally unique. Change the rule to make it possible to have projects with the same name in different project groups, but not in the same group.