Support Forum

[Dan Wager]

Is there a way to make the handler of a task be the person who is logged in? We are having problems with users forgetting to change the handler when adding a task.

[admin]

Is there a way to make the handler of a task be the person who is logged in? We are having problems with users forgetting to change the handler when adding a task.

Default handler = handler of the parent task. In your case, I suggest you create filter subscription rule that returns all tasks without handler, for example. Another possibility - wait 3.2 release, you can implement any custom logic there.

[quentin_bc]

Can you please indicate either:

a) whether it is possible to change the handler of the parent task an if so how.

b) where I can find out how to "implement any custom logic"

We're in a situation where an sysadmin person may have created the parent task for the owner of the parent task but we would want the owner of the parent task to be the default handler.

We would also not like the submitter to be able to change the default handler when the task is first created (ie on submission) but that person should be allowed to change the handler in any of the subsequent state transitions. Is this possible?

[admin]

Can you please indicate either:

a) whether it is possible to change the handler of the parent task an if so how.

Just choose the parent task and add message to select another handler (if you have permissions to add messages and change handler for the parent task).

b) where I can find out how to "implement any custom logic"

We're in a situation where an sysadmin person may have created the parent task for the owner of the parent task but we would want the owner of the parent task to be the default handler.

We would also not like the submitter to be able to change the default handler when the task is first created (ie on submission) but that person should be allowed to change the handler in any of the subsequent state transitions. Is this possible?

Please check trigger examples:
http://www.trackstudio.com/documentatio ... ggers.html

To set default handler = handler of the parent task, you needn't any custom logic. Just open category permissions and set "Can be handler = Handler" for all user statuses. This setting means, that when you create a new task of this category, only handler of the parent tasks can be choosen as handler of this task.

[quentin_bc]

Unfortunately the steps above don't seem to be enough as in the Handler dropdown I see both "gatekeeper" (the handler of the parent task) and users whose status is "gatekeeper". I want submitters to be forced to select "gatekeeper".

I am trying to make a "Trigger / Create Task / BEFORE Trigger" using the following script:

if(!task.getHandler().getName().equals("gatekeeper")){
throw new com.trackstudio.exception.UserMessageException("Please set the handler to 'gatekeeper'");
}
return task;

but this script returns an error. This is probably because I am trying to use a status rather than a user.

Please advise.

[mvasenkov]

You should set a 'Can be Handler' permission for category to 'Handler', so new task of this category will inherit handler from parent task and no one (or just users with specified roles) be able to change it during task creation.
Also set 'Can be Handler=All' permission in workflow/message types for this category.

[quentin_bc]

I have done that but I still see "gatekeeper" and those users with status "gatekeeper" in the Handler drop-down list.

[mvasenkov]

I have done that but I still see "gatekeeper" and those users with status "gatekeeper" in the Handler drop-down list.

It seems the handler of the parent task is group "gatekeeper", so all users in this group may be handlers of subtasks.

So, can you set handler of parent task to USER "gatekeeper"?

[quentin_bc]

I don't have a user "gatekeeper". "gatekeeper" is a status that is used just as a label. The idea is that each week different developers can be assigned the status "gatekeeper".

I think a script is the only way.

[mvasenkov]

I don't have a user "gatekeeper". "gatekeeper" is a status that is used just as a label. The idea is that each week different developers can be assigned the status "gatekeeper".

I think a script is the only way.

OK. Set 'Can be Handler' permissions back to 'All' and apply this Create Task/Before Trigger:

Code: Select all

task.setHandlerUserId(null);
task.setHandlerGroupId(CSVImport.findUserStatusIdByName("gatekeeper"));
return task;


Note that script force set handler to 'gatekeeper'.