Skip to content

Product Feedback

Categories

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

315 results found

  1. Make variable editing more like spreadsheet editing. The question popping up to Apply changes for each variable is not really helping. The Save button should have that responsibility.

    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

  2. View variables and environments in a way that deployments move. Lets say that I have Dev, Test & Prod. Then I'd like to see the variables from left to right grouped from left Dev, Test and Prod to the far right.

    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

  3. I was hoping the server support in 3.3 would do this, unfortunately 3.3 will only run PowerShell scripts from the Octopus Server. It would be great if the Octopus Server could have its own inbuilt tentacle for deploying packages that don't require a footprint on the target machine. SQL Server deployments and MSDeploy deployments are the obvious examples.

    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 →
  4. in the package library page (http://octopus/app#/library/packages), the Repo Status section kills somewhere around 1/3 of the usable screen space, for the entire length of the page.

    My repo contains packages with long names and descriptions, which causes significant line wrap / page length, due to the wasted whitespace caused by the repo status.

    Please move <div[@ng-show="view.filtering"]> out of the parent div/scope, so that it can take the entire width of the page (well, what's left after the sidebar menu)

    (alternatively, the repo status could move into the sidebar, but I think leaving it where it is provides better…

    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

  5. The current JSON style templates makes it somewhat difficult to manage updates and changes. When comparing a template exported from my Octopus server against one from the community library (or GitHub), most of the metadata properties are the same and aren't interesting. What's more interesting is comparing the actual Powershell script changes. But having the script embedded in a single line of JSON makes it extremely difficult to actually make a comparison to see what really changed.

    Furthermore, in our organization, when we want to make a change for a template in our GitHub branch, pull requests are difficult for…

    21 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. 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 →
  7. Hi
    In the previous version of Octopus (2.6) the 2 following properties were availabe:
    LastModifiedOn
    LastModifiedBy
    it sounds like there has been a decision to suppress them as part of version 3.x.
    As admin I find this auditing information very useful, and if anything I think that auditing should improve (it is very hard to track changes at the moment) - so I suggest to bring it back.
    See more info:
    http://help.octopusdeploy.com/discussions/questions/7091-api-change-from-26-to-3213-missing-information
    Thanks
    Nir

    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 →
  8. From the following support topic http://help.octopusdeploy.com/discussions/questions/6809-archiving-projects

    Octopus deploy does not currently support a model for archiving/unarchiving non-active or legacy projects.

    The workarounds are permission-based or user-specific but not quite what I would like to see.

    what I am suggesting is similar to Teamcity's archiving functionality. I have found this ability in TC to be useful in the 7+ years I have been using it where I have accumulated many different applications, some of which are no-longer in production, some which are in production but in maintenance mode only and those in active ongoing development.

    For the most part I only…

    35 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. We happened to be hosting https://demo.octopusdeploy.com and https://demo.octopus.com using two difference certificates, but the Octopus Manager really only supports a single SSL binding - the last one in the script wins.

    Here's an example of the script that worked using hostnameport instead of ipport:

    "netsh.exe" http delete sslcert ipport=0.0.0.0:443
    "netsh.exe" http add sslcert hostnameport=demo.octopus.com:443 appid={E2096A4C-2391-4BE1-9F17-E353F930E7F1} certhash=FAKE certstorename=My
    "netsh.exe" http add sslcert hostnameport=demo.octopusdeploy.com:443 appid={E2096A4C-2391-4BE1-9F17-E353F930E7F1} certhash=FAKE certstorename=My
    "C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe" configure --instance "OctopusServer" --webForceSSL "True"
    "C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe" configure --instance "OctopusServer" --webListenPrefixes "http://demo.octopusdeploy.com/,http://demo.octopus.com/,https://demo.octopus.com/,https://demo.octopusdeploy.com/"
    "C:\Program Files\Octopus Deploy\Octopus\Octopus.Server.exe" service --instance "OctopusServer" --stop --start

    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 →
  10. At the moment, I have to dump the $octopusParameters to the output on the PreDeploy script.

    It would be handy to have a new tab that lists all those parameters.

    -- TeamCity has a similar concept where it lists parameters used for a build

    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 →
  11. At the moment there is no way to define order for projects or project groups.

    This would be handy for all sorts of reasons but most significantly on the dashboard

    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

  12. It's very time consuming to test a change in step template.

    To test a change, a user will need to:

    1. Navigate to a project that use the step template
    2. Update the deployment process
    3. Create a new release
    4. Cancel any failed deployment in the target environment
    5. Deploy the release to the target environment

    I propose adding a few optional parameter in the create release page to stream line the process.

    1. Option to update all step templates
    2. Option to automatically deploy to a target environment (this will also cancel any failed deployment that's waiting for user action).
    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

  13. This is only a small CSS change but if you could increase the width of the "cell" that contains the project name on the dashboard that would be great. We have lots of screen space but project names (and group names) are wrapping after just 20 odd characters.

    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

  14. Any user that knows the Octopus portal URL can log into Octopus, which will create them a user on the Octopus DB and add them to the "Everyone" group, create entries on the Audit log, etc.

    Even though the user won't have any privileges out of the box, implementing a white list system to only allow people in specific AD groups to login would be something good.

    43 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. Allow cloning of library variable sets so it becomes easier to create a new variable set for a new environment.

    51 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. Nuget push is not sufficient for moving my packages from my build environment up to my octopus server, and would prefer to use FTP.

    Nuget.Server and Klondike both automatically scan the file system and add new packages to the index as they appear. Octopus’ failure to do so is preventing us from using the built-in feed.

    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 →
  17. Would like to see the ability to add metadata to machines and environments as well as a simple onhover or onclick dialog that displays the metadata. An example would IP addresses, OS versions, build dates for machines or technical owners etc. for environments in addition to a simple name.

    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

  18. If an OD setup uses a large number of Environment Variables, it can be difficult, and slow to use them for reference.

    i.e. #{EnvironmentPath}-#{Suffix}-#{SecondSuffix} isn't particularly helpful, especially if

    EnvironmentPath = #{ServerLocation}-#{ServerType}-#{TenantInstance}

    And if it nests further, it becomes incredibly slow to see how it will resolve on a deployment, short of deploying.

    If there was a way, during snapshots, or ideally through a "show resolved for : " button, then this would make it easier to reference urls from OD2.

    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. It would be really handy to say execute this step on all tentacles with the role 'FrontEnd' and 'Admin', or 'FrontEnd' but not 'OldOS'
    As it is we are managing a whole bunch of roles and tags because some applications in a project can only be deployed to machines with a newer OS and some can only go to a Task server and some only to in internal server. NOT or AND would seriously simplify the 30 odd tags we have now :)

    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

  20. We are running multiple services, each with their own IP, on the same windows server and it would be extremely helpful if we could bind the Octopus server to a specific IP. As it is now it is not certain that it will use the IP we intended it to use, which might also affect the other services.

    A simple IP choice in the binding interface would be great.

    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