Hello all, I'm looking for a solution to this:
If the creator of a task is member of a certain usergroup (i.e. customer), than he/she may only be allowed to assign tasks to persons which are member of the same usergroup (customer).
I'm curious about the responses and ideas.
Hi Anette,
You would control that with the Assignable User permission in the Permission Scheme associated with the project.
Hi John,
thanks for reply.
As Dirk mentions this is the place where the general configuration can be made.
But I would like to add an exception to that general configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Right - you won't be able to control that to that level. But I think you can have the general config and then send an email through automation if the wrong user is assigned.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is a possible solution. In the meantime I created a user picker field with a usergroup filter behind it. The value is then copied into assignee field. This way customer doesn't need assign permissions and only can choose assignees we want him to choose
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Anette Noll ,
what John mentions is indeed the general configuration on who can be assigned a ticket to. (Assignable User).
However, you can not dynamically filter based on who created the issue and what group(s) they are a member of to only allow users from that/those same groups to be assignee.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.