Hi, We are having a requirement to capture task assignee's of completed task

@ravitejavj Hi, I am not sure how you have arrived at such conclusion but afaik the value of Task Assignees(tp!assignees) won't be influenced when the Task's status turns Accepted. For instance, let's say, a Task is assigned to Group A, User 1 and User 2. Now let's assume that User 1 has accepted the Task and completed it. If a query to analytics is made at this stage, the tp!assignees returns Group A, User 1 and User 2 whereas tp!owner returns User 1.

A case where the above scenario might not work as intended is, overriding of tp!assignees because of the re-assignments of Task. Let's again take a case where the task is assigned to Group A, User 1 and User 2. Let's say User 1 has accepted the task but has reassigned the Task later to User 2 using the 'Reassign Task' functionality available in the left hand pane of the Task or the Reassign functionality built in the Task/Tempo Reports or via in-flight modifications. In this case User 2 becomes Task Assignees as well as Task Owner and tp!assignees, tp!owner evaluates to same now. It might seem that the User who has accepted the Task is also being available as Task Assignee, but the fact is that the tp!assignees of the Task is overridden during its reassignment.

If you always want to have an initial set of Task Assignees then you may store the Task Assinees in PV or as reference data in DB. Else if you want to keep track of the entire list of Task Assignees during the life span of the Task, then you need to plan in such a way that you are able to capture the Reassignment event and write data into database or populate data in PVs. Also to add, tp!assignees will be changing throughout the life span of the Task as and when the reassignment happens, so you may not be able to conclude that tp!assignees will always stay with the values with which they have been initiated.

@ravitejavj Hi, I am not sure how you have arrived at such conclusion but afaik the value of Task Assignees(tp!assignees) won't be influenced when the Task's status turns Accepted. For instance, let's say, a Task is assigned to Group A, User 1 and User 2. Now let's assume that User 1 has accepted the Task and completed it. If a query to analytics is made at this stage, the tp!assignees returns Group A, User 1 and User 2 whereas tp!owner returns User 1.

A case where the above scenario might not work as intended is, overriding of tp!assignees because of the re-assignments of Task. Let's again take a case where the task is assigned to Group A, User 1 and User 2. Let's say User 1 has accepted the task but has reassigned the Task later to User 2 using the 'Reassign Task' functionality available in the left hand pane of the Task or the Reassign functionality built in the Task/Tempo Reports or via in-flight modifications. In this case User 2 becomes Task Assignees as well as Task Owner and tp!assignees, tp!owner evaluates to same now. It might seem that the User who has accepted the Task is also being available as Task Assignee, but the fact is that the tp!assignees of the Task is overridden during its reassignment.

If you always want to have an initial set of Task Assignees then you may store the Task Assinees in PV or as reference data in DB. Else if you want to keep track of the entire list of Task Assignees during the life span of the Task, then you need to plan in such a way that you are able to capture the Reassignment event and write data into database or populate data in PVs. Also to add, tp!assignees will be changing throughout the life span of the Task as and when the reassignment happens, so you may not be able to conclude that tp!assignees will always stay with the values with which they have been initiated.