General

  1. Upload artifacts via UI

    Please add support for uploading artifacts also via the user interface.

    Uploading reports/approval documents or other files to a release is currently not possible via an upload button. We have to do a workaround using a script that uploads files from a specific folder or using the API to attach files to a release.

    Especially during Octopus approval steps people need to upload documents.

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add support for Keyfactor (Security and SSL) Certificate management

    We use keyfactor (https://www.keyfactor.com/platform/certificate-lifecycle-automation/) for Certificate lifecycle Automation. It would be great if Octopus could integrate with this keyfactor to allow for issuance, renewal, inventory, import and storage of new certificates.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support environment variables for all `octo` CLI commands / flags

    I posted about this as a GitHub issue as well (https://github.com/OctopusDeploy/OctopusCLI/issues/142). Basically, it would be nice if the octo CLI could read environment variables for all of its commands and flags. This would make CI easier since values could be easily changed and tested without having to make code changes.

    Thank you!

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow setting Build Information WorkItems

    Currently Push Build Information API and command line ignores values set on WorkItems field, only to auto populate with values once one of the Integration extension is enabled.

    Please allow Push Build Information API and Command line to
    - Set WorkItems with values set on request
    - Do not override values even if Issue Tracker extension is enabled

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  5. Subscriptions - Multiple Headers

    It would be great to add multiple headers in octopus subscription payload requests. Atm, it looks to be limited to just one.

    Thanks to this, it would be possible to better control the logic through the application that rewrites/parse the payload and send to a specific webhook

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add link/URI within the Octopus, deployment output to support one-click access from CI/CD tools

    If you use an Octopus, build/pipeline task within Azure DevOps Server/Services (or another CI/CD tool) to trigger a deployment, it would be useful to have a URI within the feedback output by the deployment within the Azure DevOps (or other CI/CD tool) build/pipeline.

    This would allow the Octopus deployment to be accessed via a single click of that URI (as opposed to having to navigate back into Octopus and find the project, the release and then the deployment).

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. codebuild

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

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

    11 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  9. Let users select apps to deploy for a Jira issue

    Currently our workflow for indicating/knowing what app/s need to be deployed for a Jira issue or a Jira release (of multiple issues) is to manually enter/bundle up these from the Jira issue descriptions which we fill out.

    What would be amazing though would be if the Octopus Jira integration plugin rendered a smart "section" into the Jira issue, where you could (1) select which apps need to be deployed (from Octopus), and (2) then get a read-only envs+releases matrix like in the octo dashboard so people can see where it's deployed currently.

    Furthermore, on the Jira release/deployment page (assuming this…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  10. JSON Template for Subscriptions

    Allow the json payload used when setting up Subscriptions to be templated in the same way as config.
    If you could specify the json with embedded octopus variables you could integrate with many many other tools without the need to add a custom step at the end of each deployment. (eg. MS teams)

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  12. Datetime filter for Octopus APIs

    Octopus does not provide date time filter for any of the Octopus APIs.
    Which makes very difficult to pull data for an older date.
    There is no way other than loading each page then take the Page.Next value and compare the date.
    Its time consuming when the date we search is really old.

    I would like Octopus deploy to support the date filter for APIs.

    There is one more drawback while using APIs with out date time filter which is explained in this page.
    https://help.octopus.com/t/date-filter-for-octopus-apis/25111/3

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  13. Trigger Deployment Through Azure Function

    Deployment trigger options are currently limited. It would be nice to trigger a deployment by executing Azure Function which would queue the request using Azure Service Bus. In this case Octopus Deploy would listen for a queue message to start a deployment.

    This solution would allow for various creative integrations within Azure.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support Azure DevOps Artifacts Universal Packages

    It would be nice to support Azure DevOps Artifacts Universal Packages feeds. We are slowly moving to Azure DevOps Artifacts (for artifact management only), and would like to use Universal Packages.

    https://docs.microsoft.com/en-us/azure/devops/artifacts/quickstarts/universal-packages?view=azure-devops&tabs=azuredevops

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support the creation of images as a task using packer

    Packer is a versatile tool, especially when working in a multi-cloud environment. It can be used for both creating both base gold images that can then be fully built on later or fully built imputable images.

    I see an octopus step being able to be used to:
    1) create or pull (from a repository) & update a json template with variables & transformation.
    2) next packer validate
    3) packer builds the image.

    ideally, there would also be an "Octopus" provisioner for packer that would allow the download of repos, call templates, transforms, variables install tenticle via cli

    but even it…

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  16. Expand Variable Conditionals to include OR/AND statements

    Currently, Variable Conditionals as documented here:
    https://octopus.com/docs/deployment-process/variables/variable-substitutions#VariableSubstitutionSyntax-Conditionalsconditionals

    Does not allow for evaluation of more than one condition, which makes the syntax really ugly and dificult to read when workaround/hacks are implemented to evaluate more than one condition...

    For example, currently only this is allowed:

    {if Octopus.Deployment.Tenant.Name == "PreProd"}prod#{else}uat#{/if}

    Make is easy to do OR/AND and evaluate more than one condition, like this for example:

    {if Octopus.Deployment.Tenant.Name == "PreProd" || Octopus.Deployment.Tenant.Name == "Production"}prod#{else}uat#{/if}

    To get an idea of the issues review this post (describes workaround for AND but OR is not possible so far!):

    https://help.octopus.com/t/run-condition-variables-two-conditions/1585

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add support for Venafi (Security and SSL) Certificate management

    We use Venafi (https://www.venafi.com/platform/trust-authority) to issue and manager certificates. It would be great if Octopus could integrate with this system to allow for issuance, import and storage of new certificates for the sites we deploy.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support DNS-01 challenge for LetsEncrypt

    Can we please have support for the DNS-01 challenge type for LetsEncrypt. We don’t want to have to expose a server to the open internet just to validate a certificate domain. DNS-01 solves this by querying the DNS provider directly for the challeng token to ensure you own the domain in question.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  19. Clone All Process Steps

    Cloning steps is a nice and welcome addition. Can we expand it to a Process level and have Clone All Steps to a different project?

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Enforce an expiry time/duration on an API key

    At present, all API keys for a user (service account user or 'real' user) do not have an expiry date.

    As a result, non-required API keys can potentially leave access open via this key.

    The suggestion would be to:
    - allow users to specify the duration of the API key/token
    - allow admins to specify the possible durations available to users/roles (e.g. administraters can stop users selecting 'unlimited' duration, and only allow 30, 60 or 90 days, for example)

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Integration  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base