Users Permissions created for logged in user on Iteration Area creation causes admin problems - by David Crookes

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 785592 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/25/2013 9:35:44 AM
Access Restriction Public


Whenever you create a new Area or Iteration it assigned the currently logged in user and assigns explicit permissions.

This creates an administration problems as if you manage by groups as is best practice, amending membership doesn't manage all permissions due to these explicit permissions that have been created.

The only way to clean up and manage is to check every single area and iteration across all projects which is not practical.  

If permissions have been assigned explicitly then they should inherit to what's being created and not require explicit setup.
Sign in to post a comment.
Posted by Microsoft on 5/2/2013 at 12:58 PM
Thanks for the feedback. We agree that it seems unnecessary to add explicit ACEs to newly created nodes for the user who creates them. We have added this to our backlog and will consider addressing it in a future release. Thanks again!
Posted by Microsoft on 4/30/2013 at 3:08 AM
Thanks for your response. We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by David Crookes on 4/29/2013 at 6:49 AM

I have attached a word document that shows
(1) The Iteration and Area security with no explicit permissions, ie. the starting position.
(2) I then add a new Iteration and area and the screen shots shows the new Iteration/Area
(3) I then how how the addition of a new Iteration and Area has also created an explicit permission for me. This isn't needed as I had the permission previously via a group and it just means it becomes difficult to administer as time goes by as explicit permissions are created whenever and for whoever creates them.

Hope this helps and if you need anything else, please let me know.


Posted by Microsoft on 4/29/2013 at 2:54 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please provide some screenshots to help us better understand this scenario?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 4/26/2013 at 10:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(