Could you create a Saved Search against the Task Assignment Object and make this the default for the Role or update the Roles Object Permissions to filter the records using the Owner Team?
Thanks! I'll poke around and see if I have any questions. - John
I don't think there is a direct way to keep the Change Management team from showing up in the list. The issue that I'm for-seeing is that the Task.OwnerTeam field is used the same throughout the solution, no matter what relationship the Task is assigned. So, for an Incident Task and for a Change Task the Task.OwnerTeam field is still the same field and the same validation/picklist is being used for both. Since the same picklist is being used, we would need a way to have a conditional picklist selection, which is not possible today. (See below for best solution from Jay. Change Management team will still show up, but you can set a validation message to appear.)
2 of 2 people found this helpful
You can create a validation business rule in Task.Assignment something like this:
$(ParentLink_Category != "Incident" || OwnerTeam != "Projects")
This will prevent the Projects team from being assigned any tasks from an Incident.
Ah yes, thanks Jay, this is the best solution! I was thinking of how to keep the Change Management team from being in the list, but with the validation error it will keep the assignments from occurring.
1 of 1 people found this helpful
Another option would be to add a constraint to the picklist based on the ParentLink_Category and the team name. Here is the pick list configured that way. It shows the team listed only when viewed from Change. I am not sure how maintainable this solution is as you try to restrict more teams by different modules. The part you can't see in the screenshot contains the expression [ValidationList]ParentLink_Category. This will show all teams for tasks from Change and all teams except 'Exclusive Change Team' under any other parent object.