Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. It would be very helpful if you provided an octopus github app in the github marketplace as a way to auth when using github feed/github credentials.

    Azure Devops and Terraform cloud currently provide this functionality and it is very helpful as it acts as an organisation service account rather than any 1 individuals account.

    Currently if I create a PAT token for octo to use and then I leave the company that puts the other development teams in a bit of trouble, not to mention the security implication of any other user in octo being able to act as me.

    13 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  ·  Integration  ·  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. We have custom urls that are generated in some of our deploy scripts - unfortunately the user has to copy and paste the url from the log into the browser currently.

    I would be nice of the logging functions supported markdown so we could just click a link to go to the url, or we could format our logs more effectively.

    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)
  3. When a release's snapshot gets stale, Octo will provide a warning when deploying the release to alert the user that the snapshot is out of date. I currently click the linked release, update the variables, and then go back to the deployment page. However, it'd be very nice to have some way to update the snapshot for the release from the deployment page itself and save a couple clicks. Could be something like a button in the warning modal that would do this.

    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)
  4. We want to be able to use a trigger to create and deploy a release of a project (using a specific channel).

    At the moment the project relies on a prompted variable so we are unable to do this.

    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)
  5. I’m actually working on a project where I need to deploy an ECS Service that uses a different FireLens configuration but the current ECS deployment step by Octopus Deploy does not support that configuration.

    AWS Docs: https://docs.aws.amazon.com/AmazonECS/latest/userguide/firelens-taskdef.html

    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)
  6. I could not find any way to get the branch name for a release in the given environment for a Project.

    My requirement: There are around 40-50 projects in my organization, there are different-2 environments like Beta, UAT and Production. and source control branches are also different-2 for each environment and there is no naming convention followed by people. So It's very hard to know for a given project and environment what is the repository and what is the branch name.

    I tried with Octopus. Client library, But could not get this information. So it would be great to have…

    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 comments  ·  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. Variable sets should have Tenant support. Such variables to have a Tenant scope.

    This would allow common vars to be reused via variable sets. This should be a common requirement for multi-tenanted microservice setups. Without that you either have to have variable copied or have them all defined at the Tenant level. Both bad options.

    A work around is to have variables as #{if TenantName =="A"}TenantAValue{#/if}#{if TenantName =="B"}TenantBValue{#/if}
    this is pretty ugly and it doesnt work for snesative variables as far as I know.

    I know this tricky to implement but really important IMHO

    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  ·  Tenants  ·  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. We're currently using Octopus to manage our Kubernetes clusters, but we're interested in transitioning to a GitOps Pull Model (rather than the current Push based approach where the Octopus Server is executing kubectl commands against our clusters) in which (in a similar fashion to the polling tentacles Octopus already offers), a service would run within our clusters and periodically
    poll both git repositiories and docker registries/helm feeds for changes and sync the cluster state accordingly.

    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

    1 comment  ·  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. ayoubkaraou

    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  ·  Tenants  ·  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. The user interface shows times in the local timezone of the client. However, when using system variables such as Octopus.Release.Created in an email or otherwise, the time is shown in UTC. While this can be converted using a script step, that would mean adding this step to every project.

    It would be great to have a variable filter that can be used to convert UTC to a different timezone.

    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  ·  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. Bicep is the new ARM in Azure. With the new Version Control feature in Octopus we've moved to putting our ARM templates inline in our deployment processes - which gives a great user experience - they can be edited either view the UI or via the repo. However if we want to use Bicep we have to go back to bundling files in NuGet packages. Can I suggest that Bicep be added as a first-class experience in Octopus similar to ARM?

    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. In my cluster we use Pod Priority classes to choose which pods to evict if a new pod cannot be scheduled. In the pod spec I need to specify priorityClassName (string, one of more pre-defined values in the cluster).

    It would be very useful for me to have this option when defining deployment in the "Deploy Kubernetes containers" step template. More info here: https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/

    https://help.octopus.com/t/option-to-set-pod-priorityclassname-in-kubernetes-step-template/28332

    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)
  13. Runbooks can be run via a scheduled Trigger. This is a very useful feature. But it would be nice if the Trigger had a feature to help when the triggered RunBook Run fails.

    I would like to propose that another field be added to the Trigger creation page. It could be called "Error Cron Expression".

    When the RunBook Run by the Trigger fails, the Trigger would switch its Cron Expression to use the "Error Cron Expression". Once the Trigger starts succeeding, then it would switch back to the normal Cron Expression.

    The idea is that, when a Trigger is failing,…

    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  ·  Runbooks  ·  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. Add additional Authentication Providers for Octopus Cloud such as AWS Identity Center or LDAP for Users hosting there infrastructure on AWS

    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  ·  Administration  ·  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. 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  ·  Releases  ·  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. The dasboard of Octopus Deploy is at our place very filled, al the environments we have don't fit on screen.
    I know there is the possibility of configure, but here you have to do a number of manipulations before the dashboard shows those environments i want to see.

    My suggestion is: It would be nice to have a filter for environment(names) in the top of the dashboard.

    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  ·  Administration  ·  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. It would be great if inside the main Octopus UI you had the option of being able to not only reach the page to download the latest Tentacle but also point the application to use that installer and be able to force-push that tentacle version to all tentacles listed in the software. For example, I should be able to download the latest tentacle version, place it in a folder on the Octopus Deploy server, then go to the UI and tell it to deploy that version to all 211 listening tentacles shown in my Octopus instance.

    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  ·  Administration  ·  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. On the Octopus website, you can see all versions of Octopus every released. Here, the recommended version for self-hosted installation is clearly tagged with a green ‘recommended’ tag.

    But on Docker hub, there is no way to automatically identify this recommended version, making is difficult to automatically upgrade to this version without having to manually look up the recommended version and then specifying the exact version tag.

    The solution I propose is to use the :recommended tag in Docker Hub to tag the recommended version for self-hosted installations.

    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  ·  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. When modifying the process of a project configured for config-as-code version control, you have the option of committing changes with a custom commit message, to a specific branch, etc. Next to that option is a "quick commit" button that commits the changes with a default commit message to the current branch.

    This quick commit option does not have any confirmation prompt associated with it, leading to the possibility of a misclick accidentally committing changes unintentionally, or with a non-descriptive message.

    It would be nice if the quick commit button had a confirmation prompt to protect against misclicks. Alternatively if there…

    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  ·  Projects  ·  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. We use Azure DevOps and the Use Octopus CLI tool installer. Right now we hard code a version of the Octopus CLI (at Octopus' suggestion) to a known working version. This has caused two issues over the last three months where the CLI version wasn't compatible with the Server. Instead of us guessing at the correct CLI version, the server should suggest one.

    The server could respond in multiple ways, e.g.

    8.* => Install latest in major version.
    7.3.* => Install latest in major and minor version.
    8.0.1 => Install exact version.
    * => Install whatever is latest.

    This way…

    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  ·  Integration  ·  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)
← Previous 1 3 4 5 72 73
  • Don't see your idea?