General

I suggest you...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. 116 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. 18 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow for specific files that were added by OctoPackEnforceAddingFiles, to be excluded in package

    I cannot not use /p:OctoPackEnforceAddingFiles=True with MSBuild. This parameter is absolutely indispensable. It is not even an option.

    However I do not want all the files in the build to be included in the package.

    The nuspec file and the exclusions ability therein does not allow to exclude files that were added by OctoPackEnforceAddingFiles.

    The effect of this is that I can’t use one of the best features of Octo : deploying to IIS.

    Because of a few files that I can’t exclude from the build, I need to deploy to a folder, remove the files that I want, and…

    30 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow new IIS step to just create IIS resources without necessarily deploying a package

    Currently the new IIS step (introduced in 3.4.7) allows you to create Sites, Apps and Virtual directories, but you always have to deploy a package.

    It might be useful for some users to be able to take advantage of the IIS functionalities, without having a deploy a package.

    Source: http://help.octopusdeploy.com/discussions/questions/9702

    225 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Automatic Logo Finder

    This is a pretty trivial idea, but I like me some logos.
    I suggest on the settings screen when you pick a logo, that octopus could automatically do what I do manually.. and that is look up the twitter account that matches my project and the facebook account and... and show the logo/avatar of each, and let me pick one of those. (perhaps give the option to put a different name since sometimes the obvious name isn't the correct one)

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Integration with Microsoft Teams

    Microsoft Teams already has a pretty great list of connectors, but one big one is missing... Octopus Deploy!

    I would like to be able to receive messages in a channel when a deployment is complete, or certain events happen.

    192 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Step for creating or updating a service in a Docker Swarm

    As a DevOps Engineer, I would like to be able to create a new service, or update an existing service in a Docker Swarm using an Octopus Step.
    For this to work for us, we would need to assign or alter Networks, Secrets, Environment Variables, and HRM Labels.
    The commands involved would be "docker service create" and "docker service update"

    30 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow named variable sets to be defined at the Project Group level and optionally shared between all projects in that group

    Within a project group it would be good to be able to define sets of variables (like in the library) which can be optionally shared between any project in the same project group. This will allow variables to be shared between similar projects and will allow easy grouping of related variables.

    7 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add "QueuedBy" system variable for obtaining user who has actually queued deployments

    I'm getting persons username when receiving deployment status email from automatically triggered deployment (by Project trigger on machine becomes available event). In the email template i'm using Octopus.Deployment.CreatedBy.Username system variable to display user who has run deployment.
    So in case of auto-triggered deployments I would like to get value "System" instead of some person's username (apparently one's who first has run the deployment manually).

    Ref: http://help.octopusdeploy.com/discussions/problems/52736-octopusdeploymentcreatedbyusername-value-is-not-system-when-deployment-fired-by-project-trigger

    67 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  10. Apply rention policy to custom install directories

    When deleting a release from a target machine according to retention policy, option to also delete the custom directory (and its contents) that release was installed to. This is for custom install directories that are named with {Octopus.Release.Number} as part of the name.

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  11. Show stats on how long a step script takes to run

    Currently the "ran for x" is accumulative.
    Whilst I agree that the UI is correct in terms of how long that block was running for it doesn't show exactly how long each deployment step is taking (essentially how long it takes to run the deploy.ps1 or some other script)

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow cloning of tenants

    It should be possible to clone a tenant including it's current configuration in a similar way to that you can clone whole projects.
    Tenants tend to be similarly configured with only minor changes to each one so it would save time rather than having to configure each one from scratch.

    133 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Visualize use of Write-Progress cmdlet in task log

    PowerShell hosts such as the PS command line and ISE visualize percent complete (as a progress bar), action text, and status text if Write-Progress is used within a script. It would be nice if the Octopus task log web UI showed that as well. Just as with other PowerShell hosts, it's not something that would be part of the permanent task log so maybe it would show up as part of the header for a task running on a particular server.

    8 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow the use of C# script (.csx) using .NET Core

    ScriptCS will no longer be supported under .NET Core.

    Please enable support for dotnet-script (https://github.com/filipw/dotnet-script) so that C# scripts can be executed under .NET Core

    11 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support ZIP file for external feeds

    External feeds currently only support NuGet package feeds. It would be good to support ZIP feeds, to support integration with products like Artifactory.

    150 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  16. Advanced Tentacle cleanup for deleted Octopus items

    Currently retention policies will only run on a Tentacle during a deployment and only for the project currently deploying. There are cases where you delete a project, channel or tenant meaning even if a deployment is run on the Tentacle those previous releases will never be deleted.

    The idea being raises will give the ability for a cleanup process to be run on an environment for all active machines. It will compare existing projects, tenants (etc where relevant) against the deployment journal and if there are records in the deployment journal that cannot be matched to the triggering instance those…

    33 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enhanced variable substitution in ARM template deployment

    When using an ARM resource group deployment, Octopus asks for parameters file, which is JSON, and replaces parameter values with matching variables.

    We would like to use the JSON variable substitution syntax mentioned here: https://octopus.com/docs/guides/deploying-asp.net-core-web-applications/json-configuration-variables-feature

    this would help us maintain a working parameters file that can be used outside of Octopus.

    61 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  18. Prompted Variables to save value per Release.

    This would allow Repeatable Release from Dev to QA to Prod.

    You would ask for value in begging of life cycle just like now,
    but for QA and Prod it would Retain that value entered in Dev as preset.

    thank you

    31 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Extend the Subscriptions feature to allow runnable scripts

    Octopus Subscriptions should be extended to include support for running scripts (PowerShell, C# etc) in response to events. That, or allow the community to write their own extensions for Subscriptions (similar to how auth extensions were implemented).

    This would save us from having to setup an external webhook for Octopus to communicate with / cut out the middle man.

    * This was originally feedback from the [Subscriptions blog post](https://octopus.com/blog/subscriptions#comment-2992150730).

    58 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Composite Step Templates

    There are sets of common steps that we very often want to "bookend" all of our deployments with. One concrete example would be: sending out a Manual Intervention to confirm when all servers are confirmed live before stamping a new deployment in NewRelic.

    Right now, everyone has to bake these steps into their own projects by adding the Manual Intervention step followed by the NewRelic Deployment Stamp step. If it were possible to create what I would call "Composite Step Templates" then I could define a reusable step template that was made up of other step templates. That way, instead…

    801 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    26 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base