My personal experience with the Traditional template is that certain
roles are not by default given the permissions that I would expect them
to have (for example, work item 160292: "a Developer should be able to
submit a build"). If you could, please submit work items for
limitations that you encounter so that these default assignments can be
improved.

So my current workaround when I want to quickly add users to a
Traditional project area is to just give everyone every privilege, and
to make their "real" role be the first one on the list (so that this
role is picked first when searching for Operation Behavior for that user).

If I have a little more time, I will modify the Process Configuration to
give Everyone permissions to do the standard things I want everyone to
be able to do. The simplest approach is to define all process in the
Project Area, and just leave all the Team Areas, Timelines, and
Iteration types alone, so all users just inherit the process from the
Project Area.

Also notice that the more mature templates (like the Scrum Template)
have evolved to the point where the role assignments are all pretty
accurate, so if you don't need the functionality provided by the
Traditional template, you might want to use the Scrum template.

Cheers,
Geoff


On 5/17/2011 11:23 AM, itengtools wrote:

Hello,

Using the Beta, created a project using the traditional template. It
creates 8 or so WIs for me, the first being create permissions.

I assigned roles (Developers to most) and Project Manager/Developer to
me.
I went to turn the WI in, and it says "access denied". Are
there any defaults for these roles or do I have to define EVERY
action. I just wanted to show a proof of concept, not study every
permission piece in the tool.

Add to that:

I just want users to submit and change WIs for the time being, what is
the fastest way to do this? There seems to be a Project Area, Team
Area, Iteration and Timeline area for WIs....which is confusing for
someone new.

any help would be useful.

thanks