Skip to content
← Navigate to roadmap.octopus.com

Settings and activity

4 results found

  1. Version rollback, or viewing of previous versions in Step Templates

    9 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Deployments  ·  Admin →
    Michael Ericksen supported this idea  · 

  2. Make step template parameters, settings and resposible teams more visible

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Installation  ·  Admin →
    Michael Ericksen supported this idea  · 

  3. Allow MarkDown files from a package to be used as manual intervention

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Product Feedback » Deployments  ·  Admin →
    Michael Ericksen supported this idea  · 

  4. hide/retire/disable step template

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Product Feedback » Installation  ·  Admin →
    Michael Ericksen supported this idea  · 
    An error occurred while saving the comment
    Michael Ericksen commented  · 

    I agree this would be great. Currently, we use conventions like "[DEPRECATED] original step template name", but a way to mark a step as deprecated, exclude it from search, and also _warn_ users that they are using a deprecated step would be ideal.