Skip to content

Product Feedback

Categories

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

315 results found

  1. Some of our ops need different dashboard views depending on what they are interested in at the time ... would be could to be able to save 'named' dashboard views that you can easily change in a drop down menu or something similar.

    36 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 →
  2. Microsoft has just released the Azure in-VM metadata service that will let you know when a machine is going to be rebooted.

    it would be great to tie this into the node maintenance functionality so that the node is automatically drained.

    It might be useful to do this for AWS as well (similar to https://github.com/scopely/shudder), but that looks a lot harder.

    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

    0 comments  ·  Installation  ·  Admin →
  3. This would make it possible to have distinct variables names in the vertical list showing its values side by side dependend on environment or target.

    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

  4. Hi.

    RE: http://docs.octopusdeploy.com/display/OD/Project+Groups

    Would be nice to have the ability to nest project groups. I have projects that are the same codebase but get released differently, and at different times, depending on the market (UK, FR, DE, etc).
    From what I can see I can only create a parent/child relationship one level deep at the moment?

    Ben

    7 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. If I want to delete a set history of NuGet packages like keep the last 20 packages on the server (Currently the only option I have is retention of number of days.) Is there a way to keep a clean-up of the NuGet based on the x number of historical packages that are needed for historical purposes?

    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

  6. 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  ·  Admin →
  7. When you create step template and set up variables, you can choose multi-line text box.
    But you cant use default value with many rows because input row "Default value" is single-line

    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

  8. In variables sets editor – filters scope - to be able to OR environments or other scope filter parameters so that it is possible to list variables in a number of environments – this would help in comparing two environments to check variables are not missing.

    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  ·  Installation  ·  Admin →
  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  ·  Admin →
  10. As a user I would like to be able to give to allow a user to deploy only on a certain set of environments or lifecycle phases

    For instance any dev to dev, any QA to QA or Staging, and ops to prod

    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

  11. Would love the ability to view the current state of my projects: At any given time either adding - or modifying projects we have many teams contribute to the overall project. Would be extremely beneficial to understand the current state of any given project : Ready for deployment - Work in Progress - Retired - Pending review - Open issues could be some of the :States" Could make them custom

    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

  12. 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  ·  Admin →
  13. The powershell editor is great, but:

    I know that there is a "full screen" button, but would it be nice, that the default editor adapts in width and height to the actual viewport?

    or make it at least a little bigger, it loks ridicoulous small on my screen.

    And there is another issue with the full screen size: the "insert variable" button is hidden (why?)...

    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

  14. We've been bitten a few times by poorly formed powershell scripts getting saved into a step.

    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

    1 comment  ·  Installation  ·  Admin →
  15. Please add search functionality to the audit log. The filtering helps but trying to find changes to a variable library for example is nearly impossible.

    23 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. By default, a Variable Set should apply to all projects, but it would be nice to be able to associate it to a specific set of projects.
    In our team, we have 13 projects that share a variable set. There's currently no way to restrict our users to only have access to those variables without having the same access to other variable sets for other parts of our organization. We don't want to have to duplicate those variables 13 times.

    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

    1 comment  ·  Installation  ·  Admin →
  17. I think project level variables and variable set level variables can be looked at in very different ways. Right now users only edit permissions based on whether a variable is scoped to an environment or not, but in addition to that, I can see a use case for allowing project variables to be edited, but not variable sets or vice versa. Conceptually these variables can be very different, and permissions should be handled independently.

    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. 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  ·  Admin →
  19. 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  ·  Admin →
  20. When we deploy branch packages as part of a patch, sometimes we are only deploying a few components of a project. The way we do this today is to create a new release, let octopus pick the latest version # for everything and then skip all components outside of the ones that we want to release.

    The problem is twofold: 1) We may make a mistake when creating a subsequent release and accidentally forget to skip a component, and then that component would slip through even though we didn't mean to push it and most importantly - 2) This process…

    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