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. Allow kubernetes & helm steps to override the target provided namespace

    Although the kubernetes target type defines its namespace, there may be some situations where a different namespace should be used for a given step

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Show variable snapshot differences in release screen

    Sometimes when deploying, the user receives this message:

    "For consistency, this deployment will use a snapshot of the variables and deployment process that was taken when the release was created, which does not include the latest changes that have been made to the project. A changed process can only be incorporated by creating a new release (this one may be renamed if desired). Variables can be updated via the release page, clicking Show to show the variables from the snapshot, and clicking the Update variables button."

    It would be great to be able to tell the user exactly what changed,…

    217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add Let's Encrypt automation to OD server

    Ensuring certificates for the OD server are up to date are a little annoying. It would be awesome if the OD server could support renewing it's own hosting certificate with Let's Encrypt.

    I've had a stab at creating custom steps to do this. The main issue is domain validation (DV). DNS validation often requires manual intervention and OD server controls http (see discussion at https://community.letsencrypt.org/t/domain-validation/26512 ).

    The only way I see this really progressing forward is if OD server supports Let's Encrypt in the server as a maintanence task as it would be able to respond to http DV requests.…

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow project dependencies - so deploying one project would automatically deploy all dependent projects

    We have many dependencies between our projects. So for example we have cross database dependencies which mean that a particular version of the database must be installed prior to another version. Similarly we have base services that are required by all others that must be installed first. There is currently no way of telling Octopus that one project depends upon another.

    We could create one great big Octopus deployment with all the steps in it to deploy the TFS projects/libraries in the correct order. But this would be very complicated because of the large number of dependencies.

    It would be…

    317 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  5. Improve variables UI

    The variables view is very basic and it generally needs improving since it quickly gets hard to use when you begin adding lots of variables.

    1. You have to add the same variable name for multiple environments and the ordering of environments is not the same. This is error prone and makes the list hard to parse.
    2. There is no description for variables so you need to add very long names sometimes. This has already been covered, but I added it for completeness. See https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6079578-enhance-the-variable-maintenance-screen-with-varia
    3. There can be different types of variables which are changed for different reasons.…

    991 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    47 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks everyone for your suggestions. We are happy to announce that a new version of the Variable Editor has shipped in Octopus 4.0! See https://octopus.com/blog/octopus-release-4-0 for more details.

    In this first release, we have focused on providing a great variable editing experience, which we hope you will love! Although we haven’t yet been able to implement all of your great suggestions, we have been able to build an extensible variable editor that we will continue to improve in future.

  6. C# Script in script modules

    We need to use C# code as script in the script modules

    229 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Improve Add Step functionality

    We are working on making the Add Step functionality much better. The idea is to show built-in steps, community step templates (from http://library.octopus.com/) and custom step templates in one central location. Please let us know what you think by leaving your comment below.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  8. Find variable usage across all projects and variable sets

    When working with library variable sets used in many projects with many steps it is cumbersome to figure out where a given variable is used.

    When updating a deployment process, certain tasks become very difficult, such as:
    -Renaming or deleting a variable
    -Checking validity of a newly-updated variable value across all usages

    With a "find all" feature these tasks would be much simpler (plus I'm sure there would be wider-reaching benefits).

    343 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →

    Happy to announce we’ve added a usage tab to the variable set page in 2019.5.4, where you can view which projects and releases are using a variable set. While this does not cover all suggestions below, we are confident that this goes a long way to solving the problem.

    Finding the usages of individual variables is something that is a lot more complex than it sounds, and we are unlikely to implement. Many variables usages are embedded in strings, or even in files sourced from packages, meaning any results we displayed would be incomplete.

    If you think we’ve misinterpreted this suggestion, please raise a new suggestion with a bit more detail about the use case, and let us know in the comments below.

  9. Automatic release creation to allow packages with variables in IDs

    Currently the automatic release creation feature does not resolve variables when looking if a package is used in a project set for automatic release creation. You can only use package IDs with static names.

    It would be great if you could use variables in the package ID and have them resolved when the package is pushed.

    Source: http://help.octopusdeploy.com/discussions/problems/28069

    217 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add an option to only create a binding in IIS if it does not already exist

    We would really like to have an option to leave bindings alone in IIS if they already exist.

    I configure a single binding as a templated deployment step. I would like octopus to automatically create the IIS app and bindings in the event the app pool and website doesn't exist - but if it does already exist I'd prefer it not to reconfigure the bindings.

    This is useful when we create website aliases for production environments which don't fit the normal QA and UAT environment setup (but they happen to use the same steps).

    Best would be a checkbox:

    "Overwrite…

    148 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add support for Python scripting.

    It would be great to see Python listed as a script step. Python is heavily utilized in the infrastructure space, AWS, F5, Citrix, VMware and will help to drive full automation further up the stack.

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Compliance with latest SemVer

    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.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add ability to indicate whether Windows Service should be started on deployment

    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.

    159 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  12 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Rather than allways taking the "latest" version of a package, can we scope the step to within a particular version range

    When you create a release, Octopus default to picking up the latest version of the available packages.

    We have multiple forks of our packages, and we need to be able to restrict a package step so that it is limited to a particular version range of the package, for example:-

    If we have a major version 1 of a package on a step,

    If we later create a fork and do work on a major version 2,

    We do not want the next octopus release to pick up major version 2 - we want to limit the scope of the…

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow me to choose which environments a project uses / per project environments

    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.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Support semver 2.0 build metadata in the release version.

    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.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. allow the Email Step to flag the email as High Priority

    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.

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  18. promote a whole environment

    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

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  19. Quick search for Releases no longer available in Octopus v4.0+

    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.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Have an option to disable the Guest/Account question on the splash screen as I always want to login with an account.

    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"?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →

    Hi Paul! You can do this already by disabling the Guest Authentication Provider: octopus.com/docs/administration/authenticat..

    You can do this via the UI in more recent versions of Octopus, or you can always do it through the command-line interface. Details are on the page.

← Previous 1 3 4 5 13 14
  • Don't see your idea?

Feedback and Knowledge Base