Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow replacements to be made over different files which share the same structure, but at a higher level requires a fuzzy match.

    This would allow us to have a singular variable for repeated applications and the change would be applied to all json files that share the same structure.

    Please see the support question below for more specific details.

    https://help.octopus.com/t/fuzzy-variable-matching/26563

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. https://help.octopus.com/t/kubernetes-certificate-variable-binding/26581

    In the kubernetes deploy step for the certificate field I have a need to use my own single text box bindable template variable rather than the current selection of certificate type only variables. The reason being that this cannot be scoped across both tenants and environments.

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. If you redeploy to Tenant and that tenant is deemed to have the latest version, then the tenant is skipped.

    Though the main reason (well for us and many other companies I've worked at using Octopus) is that we simply want to re-apply an updated variable set.

    In this scenario:
    * I don't want to redeploy the package.
    * I only want to re-run the web.config/appsetting.json transforms.

    Install of just the skip option
    (x) Skip deploy...
    ( ) Apply configuration changes only

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. It would be great if octopus has a project wise dashboard option where we can create visualization of project build stability like status of last 100 deployments , how many passed , how many failed 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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Allow copying of a runbook between projects, or a runbook template across projects, or master runbook view across all projects

    14 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 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. The Deployment Trigger should support multi-tenant logic. I am sure I do not have a unique environment that a test/staging environment is in a single tenant and production can span multiple tenants.

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Please add the name of the worker machine to the task log when a deployment is made. It is a small change which I think will be easy to add.

    Reason/Rationale/Context: We were working without workers/worker pool and we just had a few deployments that we were setting up to run on our Octopus server. My colleague added a worker and without me noticing what I thought was running on the Octopus server was moved to the worker. I knew I had the dependencies my script needed installed via Octopus on the Octopus Server (like a trusted root certificate and…

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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.

    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

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Hi it would be useful to have execute scripts feature on Octopus for data config changes to be picked from jira.
    This will help to select dev env and validate SQL and use as test evidence to run on prod env.
    Auditing abilities on octopus can be further enhanced by attaching script execution to Jira also. All major releases have database changes along with binary deployments, it is imperative we keep audit history for data changes also.

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Worker pools only are compatible with two OOTB Octopus process steps (deploy a script, deploy to cloud). My team heavily uses the 'Deploy a Package' step, but this step is not allowed to use worker pools. This is quite an oversight and should be a prioritized feature in the next sprint.

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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…

    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

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. 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

    14 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 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.

    When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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.

    53 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 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. When deploying to c:\mydirectory#{Octopus.Release.Number} Runbooks are unable to obtain the #{Octopus.Release.Number} information from the deployment. Which makes a lot of actions rather difficult.
    If it was possible for a deployment to set a variable available to Runbooks or for Runbooks to query information in releases per environment that would really be great.

    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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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.

    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

    2 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.

    Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.

    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

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. 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?

    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

    0 comments  ·  Deployments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?