Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. It would be good to have a control type of "Azure Subscription" in step templates, so that you can easily make step templates that runs under an azure subscription, rather than relying on the existing limited set.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. When scheduling a future deploy, it'd be nice if the "Deploy release" button text changed to "Schedule release" (or similar) so the user is 100% sure they are scheduling a future release without having to scroll back up and double check.
    It would also be nice to also have the "The deployment will start in approximately ...." text that currently lives under the schedule date/time picker duplicated next to the button, again so the user can easily verify that clicking the scary green button is going to do exactly what they want.

    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

    1 comment  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Now when a deployment is active, there is only a 'spinner' visible. It would be nice to see something like step 3/9 for example instead of the busy sign.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. We have an Octopus Deploy project that installs a significant number of Windows Services to a variety of servers. Quite often, we only need to deploy a partial set of the services, as a system patch.

    It would be useful to be able to define this partial deployment ahead of time so that it can be peer reviewed and signed off prior to any release.

    We tend to apply this patch to QA and then PROD environments, so this feature would potentially need to allow the user to define the subset of target machines for each environment; also ahead of…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Lifecycle phases can either specify certain evironments, or they can specify "everything that's not otherwise specifically mentioned in another phase". It would be useful if a phase could specify a pattern, and only environment names matching the pattern would be available for deployment.

    Another (more powerful and flexible) option would be environment "tagging", where an environment could have certain "tags" applied to it, and a lifecycle phase could specify one or more tags, which would either be ANDed or ORed together to get a list of possible environments.

    Source: http://community.octopusdeploy.com/t/it-would-be-nice-if-lifecycles-could-specify-environment-name-patterns/470

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Add Kerberos authentication for SSH deployment endpoints

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Octopus 2.6 used to put the current version of Octopus Server on the dashboard...I would quite like this back please!

    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

    1 comment  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Sometimes users need to deploy content to a sub directory within an Azure WebApp, but they dont want to include the complete webapp on the NuGet package. Currently Octopus will delete anything that is not on the NuGet package.

    A checkbox to avoid the files deletion and perhaps a field for "Custom Install dir" might be a good idea.

    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

    2 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. In the process definition for a project it would be really good if the sub steps under a step with sub steps could inherit the environment settings from the first step – at the moment you have to set the environments on each sub step.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. True. Powershell scripting is a powerful way of achieving more customized deployments. But not all will be well versed on scripting. Instead provide them with a UI which transforms their actions into powershell scripts used in deployments. And users can add more and more value to add by adding more actions thus making anything possible with respect to deployments. Scenarios might include taking machines out of load balancing and deploy set of services/applications and then joining them again and redo ing it for other machines. Improved and custom logging

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. I'd like to see an option added to the Configuration -> Backup tab to send an email to users in the "Octopus Administrators" team if a backup 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. It is really great to be able to add some promt variables but it could be really usefull to have anything else that just a freetext field.
    The main useful types could be checkboxes, radiobutton, dropdown list.

    Regards,
    Benjamin V.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. We would like to see all the releases that contain a specific version of a package, therefore able to track what environments they were deployed to as well as its history. When we may be debugging you can get the version of a binary and then be able to track the package and when/where it was deployed.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. We have a need to setup a Production Release Day Only team, and right now we add users to that on production release day, and then have to remember to remove those users, because we don't want them to have access to production forever. It would be nice if a team could be created that has a configurable number of days where any users in that team that have been in that team for more than that configuration would automatically be deleted from the team.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. With Octopus 2.6.4 this is partially implemented. You can see the markdown in package descriptions rendered when looking at a release.

    It would be nice to also see it rendered in the Library.

    This is extremely useful for embedding links in my packages to point back to the build and commit used to create the package.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. It would be great if you can easily see what edition you are licensed for and when the expiry for support is.

    Having it hidden in the Licence key area is not easy to see.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. As the number of scripts in the library grows it will be helpful to add more structure to it using categories and/or tags.

    Add a "category" and "tag" field to the metadata for each script in the Octopus Deploy Library.

    Change the UI to group scripts by Category.

    Initial categories could include:-

    Workflow (Wait, ...)
    Windows
    NT Service
    IIS
    Database
    Test (NUnit, Http request, ...)
    Data Collection (Disk space, CPU, ...)
    Integrations (Slack, Hipchat, ...)
    Network Environment (Load Balancers, CDNs, etc.)

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Our deployment targets encompass 100+ tenants, so our deployment process encompasses multiple products within a consistently versioned suite of products.

    When we upgrade a client, they receive all components within our suite. However, some of our products support the ability for styling customizations that we like to flow through our standard/normalized release process -- these customizations get versioned in a distinct nuget package and can be redeployed within a release version. This means that our product version is redeployed multiple times for a given client if a new customization is created for a client.

    So our deployment process for this…

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. For debugging purposes it would be extremely useful if you could have a list of variables use for at given deployment or what variables were present at creation of the release.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. As I've gotten more and more step templates, I've realized that there are some of the step templates that I'd like to rename to make it easier to "group" like ideas. The problem here is that as I refine these, each renaming creates a new version. The same would be true of the description. This doesn't seem like something I should be running out to each process to update especially since the name wouldn't update anyways.

    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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?