Support Forum

[victor]

Hello,

Scene:
- I have a project with people (manager, developers, ccb-members, testers, supporters, etc...) assigned to it. All this people take part in the change request workflow and is suggested to different transitions.
- I have other users (managers, developers...) that use the product of this project and I'd like that this people can add new change requests.
- The problem is that if I give access to the project to the last group of people then they are going to be suggested to different transitions too.

I see that this is a particular case of the mono-role restriction but I think that this is a remarkable case.

I dont know when TS is going to break the mono-role restriction, I dont know how TS is going to break it and I dont know if the solution to this scene that I am going to offer you is easy or hard to implement.

What about to give two kind of access to the projects?:
- One the actual: like a workflow participant (or partaker).
- Two a new one: like a change request producer.

Thanks,

PD: I see that this is a mini multirole feature because actually I have a producer role and if I could give multiple roles to the users I'd give producer role to all the second group people ;)

[admin]

Hello,

Scene:
- I have a project with people (manager, developers, ccb-members, testers, supporters, etc...) assigned to it. All this people take part in the change request workflow and is suggested to different transitions.
- I have other users (managers, developers...) that use the product of this project and I'd like that this people can add new change requests.
- The problem is that if I give access to the project to the last group of people then they are going to be suggested to different transitions too.

I see that this is a particular case of the mono-role restriction but I think that this is a remarkable case.

I dont know when TS is going to break the mono-role restriction, I dont know how TS is going to break it and I dont know if the solution to this scene that I am going to offer you is easy or hard to implement.

We'll implement multirole feature in the next release (3.0). It is not very difficult to implement, but quite difficult to test, so its wrong time to implement it now.

We plan to do it following way: when you give some user access to project - you can also set role for user (current user role will be default setting). So, you can set that user John has access to project A as manager and project B as developer.
Also we rewrite all code that get user role for task management stuff - it will use user role from "access control" tab when available and role from "user management" for all other cases. Role from "user management" will be used for user management tasks (who can create new users, for example).

[victor]

Great!, you have confirmed my suspicion: the TS 3.0 multirole improvement solve the showed scene.