Skip to content

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

314 results found

  1. Currently, times in the web-portal are always shown in the client machine's local time. This can make correlating events made in Octopus with those shown in other auditing systems more difficult, especially during daylight savings time.
    Many systems can be set to display specific timezones, ignoring the client machine's settings, usually UTC. It would be nice if Octopus allowed this feature as well.

    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

  2. We use datadog internally to help monitor our systems and provide insight into how our applications are not only performing but also to figure out usage patterns. If octopus deploy were able to report general information such as database pool usage and performance metrics about its internals that could then easily be pumped right into datadog or other stats providers. This could then be used to help troubleshoot clients issues a lot easier, as well as setting up alerts for people trying to manage instances. This could also be expanded to show analytics information about deployments later. Currently we made…

    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  ·  Installation  ·  Admin →
  3. Create task jobs for recurring tasks. Use permissions to control task jobs by environment, project, node.

    The QA Team could be assigned permissions on a task job to run an iisreset on all servers in the QA environment or particular projects in the environment. Dev Leads could restart Windows services on individual nodes in Dev. Right now a user has to be an Octopus admin to run a custom shell script but we don't want the Dev teams to be able to affect production. I'd rather just create a task job so Dev or QA does not mistakenly run the…

    12 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

  4. Script modules need versioning and be under source control to fully control them,

    I want to upload a package and make a call to Octo that would instruct it to create a new Script Module or to update a given Script Module with the script(s) in that package

    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

  5. Hi.
    I've a set of projects that are virtually the same except for the values in the variables.

    Right now, it is a hassle to setup the same variables in all of the projects I have and it is easy to get variables wrong (yes I use clone, which sort of helps but it is not futureproof).

    What I would want to be able to do with variables, is to create a variable set which I can consider a default value set of these variables. These variables can be overriden locally in the projects (usually necessary in development and testing…

    9 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  ·  Installation  ·  Admin →
  6. We'd love it if the Octopus Server could authenticate with its underlying Azure SQL database via Azure Active Directory Integration Authentication instead of SQL Authentication. Our Octopus service runs as an AD service account that is federated to our Azure Active Directory, but I'm still forced to use SQL Authentication at the moment.

    https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication
    https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication-configure

    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

  7. It should be possible to mark/tag a specific release.

    The reason is that we are building a lot of release candidates, but only some of those actually forms a final release, that can be installed at our customers environment.

    By marking/tagging these and highlight them in the GUI, it is possible for people to see if an official release is installed at an environment or not.
    This should always be the case in production, and it would be nice to quickly have an overview of that is the case or not.

    See also this discussion:
    http://help.octopusdeploy.com/discussions/questions/8125-marking-a-release-amongst-release-candidates

    14 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  ·  Installation  ·  Admin →
  8. When working with larger projects that contain steps within steps, the page refreshes often when making changes so this involves a lot of scrolling to find the steps you are working on. It would be great if you could collapse steps that contain children so there's a smaller list to scroll through.

    19 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

  9. When a Deployment is canceled, deployment task lists should show as canceled if they did not complete

    Currently, when a multi-step deployment is canceled, the machine shows as successful even if only 1 step is completed

    0 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  ·  Installation  ·  Admin →
  10. As an administrator, I'd like to be able to impersonate a normal user so I can see what they see when they log in.

    Currently, the only way to test the active directory groups is to walk over to a users desk and ask them to log in to verify they can't see what they shouldn't.

    Gitlab is a good example of a product that allows for admin impersonating.

    10 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

  11. Since the content type and name is obviously a unique key (particularly when exporting to files), Migrator should use the name (prefixed by the type name) as the key when linking from other resources, rather than a phony ID that changes when you import.

    That is, rather than a Team having MemberUserIds = [ "Users-1" ] it should have MemberUsers = [ "Users-BobCratchet" ] which is both more comprehensible, and unlikely to change in a simple import and re-export.

    We do modifications to our Octopus by exporting from production, importing on a dev system, altering, and re-exporting. However, the IDs…

    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  ·  Admin →
  12. We have quite a few channels. We also create a new feature branch for each feature we develop. It would be nice if I could script changing the version rules and tags via a script instead of the UI.

    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

  13. Currently in the Teams area you can either allow team access to All Environments or select which environments they have access to by including them explicitly. It would be great if we could select environments they should be excluded from (UAT, Production, etc).

    We're trying to take advantages of Azure and the ability to create test environments on the fly that allow our testers and developers to create environments for them to deploy to. Under the current access rules they need the ability to access all environments (leaving the Environments access field blank) or add each environment as it is…

    17 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  ·  Installation  ·  Admin →
  14. In the project I'm currently working in; we have 6+ environments and many variables are unique to these environments.

    To get a better overview of all the variables I suggest that you add the possibility to collapse or group the variables by name.

    9 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

  15. None of the current audit log filters (as of v3.3) make it easy to find changes to library variable sets.

    Sometimes a value changes and we don't know why. We like to know who changed it, and how long ago (and whether there have been other changes to that variable in the past). Then we can have an informed conversation about it, with those concerned.

    9 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

  16. From what I can see, there is no way to change the Polling times for Tentacle clients. The default is every 5 seconds.

    It would be good if we can configure this on an individual Tentacle basis and change the interval (maybe through the environment page).

    Due to our setup we can only use the Polling technique.

    This is our scenario:

    We have around 100 web servers spread across 3 environments, DEV, UAT & Production. We have configured this to go through a FW. As an outcome we are flooding our logs with trivial data on the FW.

    As we…

    39 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

  17. Right now you can not drag and drop a step over another. You have to delete it and re-add it. That is not effective at all and need drag and drop capability added as a feature.

    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

  18. Select multiple deployments for comparing variables used.

    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

  19. Add a documentation field in the variables view: a column for "category", or "comments" (informational only). It would be nice to be able to see that a variable is for transforms, or is data that is passed on to an external application, etc, without having to dig through the process. This can be done to some extent with variable names. However, I don't want to be changing variable names down the road just to clarify their usage.

    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

  20. In the case of custom step templates, unfortunately there is that slight disconnect between the project step and the step template itself.

    I recently came across an issue where a user tried to deploy an application through a manual intervention step. He could start "publishing" the application to the target environment, but was stopped there because he couldn't assign the task to himself, even though he was in a team with the "Project deployers" role. Turned out his team wasn't listed in the manual intervention step's responsible teams!

    Unfortunately this wasn't directly clear to me, because the responsible teams are…

    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