Settings and activity

  1. 179 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

    28 comments  ·  Product Feedback  ·  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)
    Thomas Hørup Ebling supported this idea  · 
    An error occurred while saving the comment
    Thomas Hørup Ebling commented  · 

    This would be really nice, as I ALWAYS change my mind when naming roles :-)

  2. 166 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

    13 comments  ·  Product Feedback  ·  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)
    An error occurred while saving the comment
    Thomas Hørup Ebling commented  · 

    At the moment we are solving this with workarounds. One is having 2 manual steps, one for the approval, and another for the deployment. This requires devops team to be available when the actual deployment is to happen, e.g. 2:00 AM. The second is to use the existing scheduled deployment. The governance team prefers the first option, because they like the idea, that a physical person / persons click the actual deploy button. (DevOps team are of another opinion :-)

    So I also support something like the suggest above. E.g. a new standard step called something like "Async Manual Release Approval".

    If there is a powershell ninja reading this, perhaps they could suggest a custom step?

    Thomas Hørup Ebling supported this idea  ·