Peter Bollwerk

My feedback

  1. 118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Peter Bollwerk supported this idea  · 
  2. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Peter Bollwerk commented  · 

    I meant that you can't create a copy/clone of a variable set using the UI, as far as I can tell.
    However, with these cmdlets, you were able to export a variable set to an XML file, edit it as needed, then re-import that XML and populate a new variable set with the values.

    Peter Bollwerk shared this idea  · 
  3. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General » Deployment features  ·  Flag idea as inappropriate…  ·  Admin →
    Peter Bollwerk shared this idea  · 
  4. 447 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Peter Bollwerk supported this idea  · 
    Peter Bollwerk commented  · 

    I would like to add my voice to this request.
    We have the same issue as Andy.
    We are forced to allow a team to have inappropriate access to Projects they aren't involved with, just to be able to edit a Variable Set.
    Please add the ability to scope a team to specific Variable Sets, as you currently do for Environments and Projects.

Feedback and Knowledge Base