Support Forum

[cwensel]

took me a bit after reading the docs to see that 'status' is overloaded.

its a 'group' for permmissions, and
a 'role' to manage capabilities in the workflow.

if that's realy the case. will a future version break those out?

and if so, can a user be allowed to have multiple roles (viewer and tester, or developer and tester, etc)

ckw

[admin]

took me a bit after reading the docs to see that 'status' is overloaded.

its a 'group' for permmissions, and
a 'role' to manage capabilities in the workflow.

if that's realy the case. will a future version break those out?

and if so, can a user be allowed to have multiple roles (viewer and tester, or developer and tester, etc)

ckw

I think that all OK, its the same objects. Define some permissions or rules for each user seems like not so good idea, define generic and user-independend process can be better. So, when we assign user to some group (status) we give them consistent set of permissions/capabilities.
Of course, some functionality (such as email notification) can be customized on per-user basis too.

Multiple roles does not supported yet, but we plan to implement different roles for different projects - when you add some user to Access Control List (ACL) you will also define their role for this project - developer for project A and manager for project B.

[cwensel]

for tracker studio, there probably isn't much value in having 'groups' and 'roles' instead of just 'status'.

but allowing a user to have multipe roles in a single project and across projects would be nice. but again, i'm still learning track studio, so it may not make sense as it's implemented.

but yes, a user may be a 'tester' in one project and a 'developer' in another. (there are probably better examples) it would be nice to have.