General

  1. Use AWS IAM Roles as Octopus AWS Accounts

    When creating an Octopus AWS Account (https://octopus.com/docs/infrastructure/deployment-targets/aws) you currently need to enter an AWS Access Key and Secret Key. This means the corresponding AWS Access Key needs to be periodically rotated, creating some management overhead and potential security vulnerabilities. Rather than an AWS Access Key and Secret Key, if we were able to enter an AWS IAM Role that is assumed whenever that Octopus AWS Account is used, then we would no longer need to manage AWS Access Keys.

    In the background, Octopus Deploy would need to set it up so that the AWS IAM Role is assumed…

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ability to set application URLs for each environment, allowing linking from dashboard

    It would be great if the Octopus dashboard, which displays the current releases of each application in each environment, contained links to the applications in the specific environments. E.g. if the box displaying details of the most recent deployment of Application X to Environment Y also contained a link to that app in that environment

    We presently maintain this info outside of Octopus, in Wiki pages etc, but it’s a pain to maintain.
    It would be great if this was directly available in Octopus, because the matrix of applications to environments is already there. Forcing users to access the links…

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

    Add an official Octopus plugin for AWS CodeBuild to integrate with Jira.

    https://octopus.com/docs/managing-releases/issue-tracking/jira#availability

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Integration with Azure App Configuration

    Please provide integration with Azure App Configuration. We need the task to download variables in the process runtime. This will allow to use Azure CMDB and Octopus for deployments.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Support older versions of SQL Server

    Please reintroduce support for SQL Server 2016 Enterprise.

    Recent versions of Octopus only support SQL Server 2017+. SQL Server 2016 (SP2) still has mainstream Microsoft support until July 2021 and extended support until July 2026. It is very expensive for organisations to run and support multiple editions of Highly Available Enterprise SQL clusters and is consequently a barrier for upgrading to the latest Octopus version for my organisation. My organisation is a large enterprise in a heavily regulated industry so our software must be supported platforms, I am sure many of your enterprise customers would benefit from this.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Runbook need support for prompted variables

    Runbook need support for prompted variables

    We need support for prompted variables when using runbooks hope this is added in a future version

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  7. Expose Octopus.Deployment.Targets during deployment

    The current Octopus.Deployment.Targets variable is only available to the Deployment Changes section. It would be beneficial to expose this information during the deployment too.
    The use case in mind is sending emails pre-release that mention the machines that will be deployed to, or in the case of Azure, could expose the URLs, given these work on the convention of <machine-name>.azurewebsites.net

    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 →
  8. Allow variable in variable set to have a Project Group scope

    It would be useful if we could set variables in a variable set to a Project Group scope.

    The use case for this is that we have a shared variable set that sets a product ID.

    We could then scope this by product group.

    eg

    Variable Set Products
    Product Id - ATeam Scoped to Project Group A
    Product Id - BTeam Scoped to Project Group B

    Project Group A
    - Proj A1
    - Proj A2

    Project Group B
    - Proj B1
    - Proj B2

    Currently we have to override the ProductID in every project in Project Group B which sometimes…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add more regional support to Octopus Cloud

    Octopus Cloud is presently limited to three Azure regions (West US 2, West Europe, Australia East).
    Strict data sovereignty rules for some customers may mean that Octopus Cloud is currently not a viable solution.

    It would be good if more regions were supported by Octopus Cloud - specifically UK West and/or UK South.

    Also - how does Octopus handle high availability and fault tolerance if limited to only one region?

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  10. Disable the 'Deploy' button whilst filters are being refreshed and affected tenants loaded

    Whilst in the deployment screen, the 'Deploy' button should be disabled whilst filters are being refreshed and affected tenants loaded.

    With the current functionality, it's very easy for a user to add a tag filter and not realise that additional tenants have been included, but are not yet visible in the 'Preview and Customize' section. The loading bar at the top of the box is subtle and easy to miss.

    Once affected tenants have been refreshed, the button should be enabled again.

    22 votes
    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 →
  11. prompted variable calculated default value

    Allow the default values for prompted variables to be calculated, instead of a constant.

    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 →
  12. Runbook specific variables

    Add variables to Runbooks, so that adding new variables to the project for a specific Runbook don't cause the snapshots of other Runbooks to be old.

    For example, we have a Runbook that exports data from a database to a CSV and emails it. We have variables for the from and to dates and the email addresses to send to. The from/to dates are prompted variables, so you can do an adhoc run. If no dates are provided, it will default to the last week of data.

    These variables only have meaning for this Runbook, so it would be nice…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add date, time and date/time variable types

    Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.

    Optionally provide a friendly interface (date picker control) for the respective values.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  14. Tenant "overview" page is not intuitive

    I find that the most common task performed on tenants is modification of tenant variables. However, I feel that the UI does not support this task very well.

    I find that once I click through on the tenant, my next step is to click on the project in which I wish to set variables for which does not result in the expected action (it takes you to the project instead).

    My recommendation is that the tenant variables becomes the landing page for tenants and the project administration for the tenant could become a secondary page (or perhaps it could even…

    2 votes
    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 →
  15. Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

    Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow a runbook to be able to be run from another runbook

    With standard octopus deployment there is a "deploy a release" step which can be used to run other projects from a parent project.

    It would be usefult o have a similar "run a runbook" step to be able to build up run books from smaller steps into bigger processes.

    Our use case is swithcing to DR, there are numerous steps such as stopping various services, starting other services, stopping replication etc. But, each of these steps is also useful in itself so we have steps effectively duplicated, once in the invoke dr runbook and once in a runbook all by…

    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 →
  17. Include description field for project and library set variables similar to project template variables

    It would be helpful to have a description field for variables in a project or in library set variables. I know the idea of having 'descriptive variables' usually solves this issue but sometimes across teams it doesn't always happen.

    To save screen space it could be a descriptor you enter when making the variable then when you mouse over the variable it shows the information descriptor.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Process Editor with parent/child steps to frustrating.

    When I have a few Parent processes with some Child process in them, The Process Editor is very hard to use. You get that dreaded "Menu Options unavailable while viewing a parent or its child steps." Comment box appear. The problem is that there is no other way to do Parent tasks like add a child step now that you have a "parent or its child steps" selected. Only when you click into another Parent step can you access the Parent process menu. This is hugely frustrating when you are working of creating a bunch of child steps.

    Please change…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Add support for SVN (subversion) VCS commit information

    After pushing build information from a TeamCity project that was building some code from SVN (subversion) version control system, I noticed that while the package in octopus did have the commit section filled out as expected, the commits were NOT there when creating a release with that package. This meant that we couldn't automatically generate the release notes based on commit messages. I contacted octopus support and we eventually figured out that SVN is not supported.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  20. 'dotnet octo pack' multiple packages in one command (Octopus.DotNet.Cli)

    The OctoPack project is great for Framework projects. We add the nuget dependency to select projects and add /p:RunOctoPack=true to our build script. The build script does not need to be updated for every new, removed or renamed octo-packed project.

    SDK projects are less automated. After building, we have to run dotnet publish, then octo pack for each project. It would be great to define 1 build script, then update the projects as needed to pack or not.

    Idea to attain goal:


    1. Add element &lt;IsOctoPackable&gt;true&lt;/IsOctoPackable&gt; in csproj that works similar to IsPackable.


    2. Allow dot net octo pack to point…

    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 →
← Previous 1 3 4 5 67 68
  • Don't see your idea?

Feedback and Knowledge Base