Product Feedback

Product Feedback

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. We need permissions around Step Templates. These need to be for: creating, importing, exporting, deleting.

    0 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  ·  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 would like to have the best uptime in our production environment, so we use rolling deployment. In QAT, though, we don't care about uptime. It would be nice to have the rolling deployment option be chosen based on environment

    0 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  ·  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. having a variable to be able to define your own package installation directory is needed. We have a situation where we rely on roles to define variables for customers, but the package on the same environment will not install if it already has been, even though it needs to be re-extracted for the role variables to be applied. Having to force the package redeployment on all projects then takes a lot longer than it should. Having the ability to add role to the path of the package directory would stop this from being an issue for us. Something similar to…

    0 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  ·  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 need an option in the retention policy to allow for keeping the last updated package in the repository 'always'.
    There are cases where the latest release does not included the latest package, but that package may still be needed later on.

    Source: UV 941

    0 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  ·  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. https://github.com/OctopusDeploy/Issues/issues/264

    When displaying snapshots, show any variables whose scope values don't appear in the current set available to the project (owner)

    At the start of deployment, warn if scope values have changed (e.g. if Production is deleted and recreated, there will be a variable scoped to the old Production environment ID, apparently useful but not applied)

    Where the name associated with a scope value has changed, show the old and new names

    0 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  ·  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)
1 2 68 69 70 72 Next →
  • Don't see your idea?