Why Do I See a Group's Tasks in my Task List, Even Though I Do Not Belong to the Group?

Summary

When using the Dynamic Group Shape, users who are not part of a group sometimes see the group's tasks in their Task Lists.

Applies To

• Dynamic Group AgileShape

Details

When using the Dynamic Group Shape, users who are not part of a group sometimes see the group's tasks in their Task Lists. The users cannot access these tasks. When they click the task name, a message appears, "Task does not belong to you."

This issue occurs because, to optimize system performance, groups' and roles' tasks are displayed in users' Task Lists based on partial matches to the value of the Group/Role Name property in the Dynamic Group AgileShape. The Group/Role Name in the Dynamic Group shape is compared as a partial match, rather than an exact match, to all group and role names Tasks assigned to other groups and role names for the purpose of displaying tasks in users' Task Lists.

For example, if the Group/Role Name is set to Reviewer1, the Task List will return tasks for groups or roles named Reviewer1, Reviewer11, and Reviewer12 because Reviewer1 is included in all of these names. If, on the other hand, the Group/Role Name is set to Reviewer11, the Task List will not return tasks for groups or roles named Reviewer1, or Reviewer12 because the full string Reviewer11 is not included in either of these names.

The fix for this issue is to use one group or role name that is not a shorter version of another group or role name. For example, avoid group or role naming conventions like Reviewer, Reviewer1, Reviewer12, Reviewer123.