In Octopus 1.6 we were able to disable all steps and then select only the steps we wanted. We have 30 steps and on any given release we want to only run 5 to 10 steps. It would be nice to have the disable all steps option again.

We embed the JIRA's resolved in this sprint into the release notes, in markdown syntax to get hyperlinks to issue and changeset. We also send e-mails out to testers, etc, to let them know what is included in the current release and they can promote to their test environment based on the fixed issues. I would like to embed the release notes in the e-mail, however no e-mail clients (besides gmail of course), support rendering mark down.

So the feature could parse the markdown to either plain text or html, based on the setting in the e-mail step

Currently the Tentacle health check seems to consist of only "Is the service running?". It would be very useful to make the Tentacle run a custom PowerShell script on health check.

Alternatively make it possible for the health check to check for diskspace, which is what we currently need.

I'd like to be able to send an email (the same, templated email) for all deployments to a specific environment. This way I wouldn't have to create an email notification step per project.

The radiobutton to select "specific version" for each package of a release should automatically be selected when the user types (or pastes) a version number in the textbox.

Hi,

In cloud environments you add and remove servers. Ideally it would be great if we could add a server and its relevant role and octopus would deploy the version of each project currently deployed to that environment and role to bring it up in line with the other servers in that role.

Cheers,
Andrew

We have environments that are isolated environments consisting of VM's sitting in their own networks. The only way in/out the isolated environment is via a management server (or jumpbox) Having the Server calling Tentacles forces us to set up port forwarding on servers.

It would be great if a Tentacle could query the server instead of server calling it. All communication would be going out of the isolated environment.

I want to deploy octopus release notes. My octopus server is internal only. If I could just run something on the server I would be able to query the api, do any formatting and put it on my server.

We have defined a rule, that only our Ops team can see ProductionTest and Production environment and this gives a bunch of headaches.
- Not being able to define global variables
- Forgetting to set dependent variables i ProdTest and Prod
- Not being able to see non-sensitive variables in ProdTest and Prod
- Overhead for Ops, setting up non-sensitive variables

Suggestion: Add the possibility to mark a single variable as sensitive.

In Projects/Releases/Deploy Release, the "Deploy to" should default to blank, forcing the user to select an Environment. This will prevent deployments to the wrong environment.

For emails, it'd be nice to have the deploying username/email available for something like email steps and others.

Because of time-zone differences between the Octopus server and one of our tentacles it took me a long time to realize that the wacky timestamps I was looking at were just 12 hour clock formatted, without the AM/PM suffix.

I'd most like 24hr format, but I'll be content if the AM/PM designation was added to the existing format. But what's there right now is confusing and easily misleading.

I would like the option to return XML instead of JSON for all /api calls.

When you have a long value in a variable it is difficult to see the whole value. It gets cut off in the grid and I have to inspect the HTML to see the whole value.

I would be nice if there was a hover popup or tooltip with the full value.

Currently, octopus deploys are either successful (green) or unsuccessful (red). We did an octopus deploy the other day to our two node web farm. Node1 deployment was successful while Node2 deployment was semi-successful (files were deployed but app pool and virtual app did not exist). Would be nice to have a yellow status code to indicate partial success (success with warnings).

If 2 users edit the Octopus Variables for a project and click save they should not overwrite the other users items.

Configuring anything other than a trivial permissions setup is horribly time-consuming. Granting a specific group a specific set of permissions, for a specific set of environments requires the creation of multiple permission grants, each of which has to be created from scratch since there's no 'copy' button next to the existing permissions.

Changing the select permission/environment/group drop downs to multiselect would fix this in one fell swoop, and make the intent of otherwise disparate permission grants much easier to divine.