Support Forum

[victor]

Hello,

Some time a go we define a new 'actor' that could for example: process a message. This was the 'submitter & handler' actor.

This was applied to transitions and categories in TrackStudio 2.8.

Well, today I found a (maybe) interesting new 'actor': 'parent task handler' or maybe the 'parent handler' (o phandler like abbreviation).

I am going to explain how I found that this could be useful.

I have a big 'bug' workflow with a manager like the main role and other roles: developer, ccb-member, tester, supporter, customer.

Well in a project-X user-A could be the project leader and then user-A must have the manager role. In other project-Y user-B could be the project leader and then user-B must have the manager role.

But if user B is a developer in project-X I have a known problem because trackstudio has only one role by user.

This suppose that if I have a state where only the project leader must be assignable I cant do it and I have to allow all manager to be assignable.

But I found that I can determine who is the project leader because he is the handler of the project folder, where the bugs are added.

Then if I could say 'these transitions only can be processed by the parent task handler' I shall solve the multiple leaders problem.

Ok, thats all, I comment the reason for find useful this 'actor' because I thing that maybe you are going to solve the problem of an unique role for a user in all the system and then I dont know if this new actor would be so useful.

Thanks,

[victor]

Hello again,

Thinking about it I found another scene where this 'parent task handler' could be useful.

I have defined a 'bug' category. Inside a bug I can define subtasks named 'activities' that are assigned to developers to solve the bug (a big one of course).

I want that the handler of the bug can send messages to the activities developers... Tachan!... now I need a 'parent task handler' to say in the 'activity' workflow that I like that a specific message could be sended by the bug handler (this is: the parent task handler).

Maybe I'd discuss this possible improvement analyzing this scene.

Thanks

[admin]

Maybe I'd discuss this possible improvement analyzing this scene.
Thanks

I need some time to think about possible side effects/drawback before I can discuss it, but I like this idea.

[victor]

Maybe I'd discuss this possible improvement analyzing this scene.
Thanks

I need some time to think about possible side effects/drawback before I can discuss it, but I like this idea.

Hello,

Is there any new about these side effects?

[admin]

Maybe I'd discuss this possible improvement analyzing this scene.
Thanks

I need some time to think about possible side effects/drawback before I can discuss it, but I like this idea.

Hello,

Is there any new about these side effects?

Does multi-role fix this problem. For example, when user both manager and developer for some project, but only tester for another ?

[victor]

Does multi-role fix this problem. For example, when user both manager and developer for some project, but only tester for another ?

Yes, you are right with multi-role we solve this problem.

Then I present it for your consideration about future versions: This option could be an authomatic re-role facilitie. If I can change the project leader I change the project handler and the users role. Well, with this improvement a customer could define the workflows with parent-task-handler basis and then with only changing the project handler all the rest would be readjusted.

For your consideration.