General

  1. 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 →
  2. 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.

    19 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 →
  3. Right-click "Open link in new tab" no longer working

    This was previously asked for and done here https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/3133236-non-javascript-based-links

    But we updated from 2019.6.8 to 2019.9.10 and this has broken in at least one spot.

    If you click "Project switcher" and search for a Project the dropdown no longer gives links that can be open in a new tab.

    This makes me sad. :(

    11 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 →
  4. Deployment promotion with excluded steps is not persisting chosen steps

    Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.

    We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.

    It would be great if you can persist the state of excluded steps to the next environments as part of same release?

    15 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 →
  5. Allow the visibility of what teams have access to a project/group

    Right now you can view a Team and see what project or project group that team has access to. We'd like to see the reverse as well. When we go to a project or project group we'd like to see the teams that have access along with their permissions.

    10 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 →
  6. Support Terraform 0.12

    Octopus supports Terraform-Steps. It uses Terraform 0.11. Terraform 0.12 has been released and has a few breaking changes. Update the Terraform-Integration to be compatible with Terraform 0.11 and 0.12.

    36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support inserting into an array in JSON Configuration

    Given an JSON settings file which has an array element

    e.g. { "Users": [] }

    Use Octopus variables to insert into the array rather than just replace values.

    e.g.
    define Users:0:Username = user
    define Users:0:Password = password

    Would result in the object getting inserted

    { "Users": [ { "Username: "user", "Password": "password" } ] }

    https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7

    9 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 →
  8. "Acquire Packages" should be first step

    Give an option (or make it default) to have the "Acquire Packages" step to always happen at the very beginning.

    Our use case:
    We uninstall a program, then extract the package and install it. If it fails on the package download (which happens automatically right before the extraction), then our deployment target had all of its files deleted, but failed the deployment.

    Our current fix:
    Make sure the "Extract Packages" step is the first thing in every project, to force "Acquire Packages" to be at the very beginning

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  9. Use IAM roles instead of AWS access secrets for all external resources, e.g. feeds, targets, community library tasks

    Currently, the only way to set up AWS authentication for an ECR external feed, AWS deployment target, community library task, etc, is with an IAM user secret such as API access keypair. Our product secrutiy team has exlicitly forbidden use of secrets such as keypairs like this and requires everything to use IAM role authentication via role assumption.

    It would be lovely to replace the access key and secret key inputs with a single input for an IAM role name to assume into in order to get the needed credentials. The authentication and login could then execute on workers with…

    29 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 →
  10. Connect project to many tenants at once

    There is currently no way to associate a project to multiple tenants without going into each tenant one by one, finding the project, selecting an environment, and clicking Save. For installations with many (tens or more) tenants, this is quite inconvenient, and has resulted in hacky workarounds from third-parties.

    4 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 →
  11. Tenant variables side by side

    The idea is to have the tenant variables displayed vertically, with one column for each environment.
    Currently, it is quite tedious to compare or copy variable values from an environment to another.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for High Priority Deployments/Tasks

    Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
    In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
    This is not possible now, the only solution now is to cancel all the existing tasks.

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support toast messages

    It would be useful to notify either all users, a team, an individual of some changes (step template to be deprecated, upgrade occuring) via a toast/message on login so that important messages related to Octopus/deployments are delivered via Octopus directly to the users that need to know.

    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 →
  14. Support linux-arm in Linux Tentacle

    A dotnet core version has been build. I would be great if this was compiled to a linux-arm runtime.

    https://octopus.com/docs/infrastructure/deployment-targets/linux/tentacle

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add a view that shows all Releases across all channels and Tenants

    Please can a view be added that allows a user to see all deployments in a pipeline, spanning all tenants and channels? Having to search for these seperately causes no end of headaches as I often have to line up versions and this is made harder when they have to be searched for. Making it so they are all visible from the main page of a release as an optional view would alleviate this.

    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 →
  16. Ability to copy from logs without getting timestamp interwoven

    The current implementation of Octopus Deploy makes it very difficult to copy information from the log output. The resulting copy of multiple lines includes the date information interwoven with the log data. This makes it almost impossible to copy from Octopus to create a bug in Azure DevOps.

    Attempting to copy this information results in a test block like the following:
    Failed TestPagesAreLoadingLoginPage
    December 19th 2019 08:44:12
    Info
    Error Message:
    December 19th 2019 08:44:12
    Info
    Assert.AreEqual failed. Expected:<200>. Actual:<404>.
    December 19th 2019 08:44:12
    Info
    Stack Trace:
    December 19th 2019 08:44:12
    Info
    at Platform.Specs.SystemResponsivenessSteps.ThenIShouldRecieveAMessageBackFromTheServer(Int32 p0) in H:\Agents\DEP-3_work\2\s\Platform\Outsell.Tools\TestFramework\Platform.Specs\SystemResponsivenessSteps.cs:line 137
    December 19th

    4 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 →
  17. Tentacle authentication should be able to use .pem .key.

    Tentacle authentication happens only using .pfx cert, but it should also use the .pem

    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 →
  18. Allow MarkDown files from a package to be used as manual intervention

    Some of our deployments have lengthy steps that cannot yet be automated. It would be great if markdown files contained with in a package can be used as manual intervention steps in a deployment.

    I was thinking this could work by simply having an option to choose a file rather than type the instructions on a manual intervention step.

    However it would be really great if some naming standard could be introduced. For example "PreDeploy.md" would appear as a manual intervention at the start of the deployment.

    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 →
  19. Retention policies on offline targets (artifacts)

    Delete previous install files when new install (with an artifact) occurs (offline targets). These deletion should keep in mind the configured retention policy in the corresponding lifecycle

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
  20. Encrypt variables using Certificate

    Add the ability to encrypt variable strings using something similar to the variable filters.

    Something like: #{VariableToEncrypt | Encrypt(#{CertificateVariable})}

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 66 67
  • Don't see your idea?

Feedback and Knowledge Base