> You are right. User with role SCRUM_MASTER has also role TEAM_MEMBER,
> because he also takes part in development. As I know role SCRUM_MASTER
> master is equivalent to lead engineer so it is normal for him to take
> part in development. At least this is my opinion and also many scrum
> materials describe role in such way.

True.

> I am not sure, but I think that user with role TEAM_MEMBER is
> forbidden to switch tasks on whiteboard that he doesn't own. So if
> this is true, role combination SCRUM_MASTER + TEAM_MEMBER means, that
> because user is SCRUM_MASTER he has rights to switch tasks, but
> because he is also TEAM_MEMBER owner is changed. On the other hand
> role TEAM_MEMBER doesn't have rights to move tickets (I am not sure
> for changing owner).

Yeah, SCRUM_MASTER gives him the right to move the ticket even though 
it's not his, and TEAM_MEMBER gives him the right to accept it - and in 
the combination thats why the quick owner change UI isn't shown. :/

> Is there a way to disable automatic owner change when switching tasks
> for such user?

Right now it's not. Right now you can create a separate account for the 
scrum-master so he doesn't have both TEAM_MEMBER and SCRUM_MASTER rights 
at once.

This is definitely something that we want to fix though, and we will do 
so in the next sprint.

HTH
-- 
Mit freundlichen Grüßen
Martin Häcker
Consultant

agile42 GmbH
www.agile42.com
Grünberger Str. 54
10245 Berlin, Germany

Office:       +49 30 2005 3958
Fax:          +49 30 2007 8274

Amtsgericht Charlottenburg: HRB 111402
CEO Marion Eickmann


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to