Product Feedback

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Cloud region health checks

    It would be nice to define health checks for a cloud region, ideally a script that is run for each deployment in the region.

    It's easy to deploy websites to a cloud region, but hard to see if they're up and available.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Dashboard should be better at visualizing multiple tenants

    Currently the home dashboard displays tenants as a small grey-on-grey count of up-to-date tenants vs total tenants. It would be nice to see a coloured pie chart or similar visualization instead, to make it more obvious when one tenant in an environment is still running an old version or has had a failed deployment.
    It can be easy to miss failed deployments from the dashboard screen.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow setting Build Information WorkItems

    Currently Push Build Information API and command line ignores values set on WorkItems field, only to auto populate with values once one of the Integration extension is enabled.

    Please allow Push Build Information API and Command line to
    - Set WorkItems with values set on request
    - Do not override values even if Issue Tracker extension is enabled

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Operations Dashboard

    I use Runbooks to check things in my Kubernetes cluster. I can run these on a trigger, but I have no way to surface them if there is a problem.

    It would be really useful if Octopus Deploy had a dashboard that had configurable "Widgets" (or some such thing). You could have several different kinds of "Widgets", but the simplest would be one that has two states, "Needs Attention" or "Fine" (along with some text for context).

    So I could define one of these Widgets, lets call it Container Base Image Status (a real example for me). In that widget…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add tenant tag support to runbook scheduling

    Instead of only allowing explicit tenant selection, add the ability to select the tenants to execute the runbook for by their tenant tags when adding an new scheduled trigger.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support Terraform Registries as an External Feed

    I would like to use a Terraform Registry as an external feed. This would allow me to focus on certain versions of my terraform code fordeployment.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. ID and Name in the html code for SIGN IN button?

    We are trying to add our internal Octopus url access through CyberArk privileged access security, but CyberArk is not able to detect the "SIGN IN" button in the login page. Cyberark support said this is due to inspection of the "Sign In" button do not have ID and Name in the html code so Cyberark can't find the element.
    Please can you help us add the ID and Name in the html code for SIGN IN button?

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Tenants

    Display Tenant Name and Description when making selection of the tenant when deploying a release. An environment made by a previous team used the "Name" field to enter some sort of "Id" and on the "Description" field they captured the tenant's name, now is somehow hard to know which tenant to select by means of the Id.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Control when Tentacle retention policy step will be executed during deployment

    Tentacle retention policy is executed once all deployments steps are completed. When the retention policy step starts running, it blocks any other step.
    This behavior is by design and can't be configured.

    This design can cause issues if for some reason the retention policy step encounters issues and takes a long time to complete.

    As a workaround we can add a deployment step of a dummy package at the end of the deployment process. As result the tentacle retention is executed at the last step of the deployment.

    I would like to have an option to control when the retention…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add parameters to Runbooks

    This would be like runbook specific variables, but they are defined on the runbook and don't make sense to be in the published snapshot. They would generally be prompted values, but that shouldn't be required. They would be "snapshotted" when you run the runbook. When you are scheduling runbooks with a trigger, you should be able to provide values to use when the runbook is triggered.

    For an example use of these, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Dashboard icon page target

    I manage a multi tenant system and the dashboard is always a pain to use.

    First the icon cant be trusted as it dose not accurately show things like a single tenant deploying (The animated icon).

    But the real pain is that if I click that icon it takes me to the deployment page of one of the tenants. What I want it to do is take me to a screen for all of the tenants. Something like the tasks screen filtered by environment would be very nice.

    Then I would be able to see the true state of all…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add timeout to guided failures

    Add an option to have guided failures timeout out and fail after a specified period of time. I.E it no manual intervention is taking in 1 hour have the deploy fail completely.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow variables to be set as Environment Variables

    It would be extremely useful to allow variables to be set as an environment variable before the process starts (and even allow outputs to be made environment variables). At the moment it is extremely hard to write generic scripts for both development and for use in octopus.

    Allowing variables to be set as environment variables eliminates this issue as well as allows more providers etc.

    If I take a terraform run where the provider (say digital ocean and terraform cloud) can be initialized via environment variables I do not need to litter my scripts with octopus only if conditionals. They…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to limit updates to specific variable sets to specific groups

    We'd like the ability to lock down a specific variable set so that only specific teams can update the values in that variable set. We want to be able to have variables that multiple teams consume but only admins can set the values.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  15. Octopus Server on Linux directly

    As a Octopus Administrator I should be able to install Octopus Server directly on Machine with Linux operating system.

    Now, there is only version with Linux container and in some cases docker can be unnecessary abstraction layer, that need to be maintained with OS machine.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  16. Marking a process step as non critical

    Some steps in the deployment process could merely be just to trigger some notifications or sending metrics to other products. These steps are not critical to the deployments.
    A flag in the step could be helpful which can mark it as a critical/non-critical step

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Create deployment step skipped or failed as subscription-eligible events

    We would like to get notices when any deployment process either skips a step (for instance because there are no available targets) or when a step fails.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  18. Cloud: Support my local time zone

    I would expect there to be a place in setup where I could enter my local time zone. Then subsequently all dates/times would display in my current time zone. This would include dashboard dates/times as well as Release Versioning.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →
  19. 1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Support for More Runbook Triggers

    The only Runbook trigger right now is a scheduled trigger.

    I would like to suggest two more trigger types:


    Helm Chart Package Trigger:

    When a new Helm Chart version of a package is published, then the trigger would fire. (Allowing the calling of a Runbook.)


    Version Control Trigger:

    If Octopus Deploy added a VCS trigger, then it would allow us to use GitOps.

    Both of these allow Operations to enable control from check in / merge point in source control.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base