Allow Delegated Tasks to Pull into Lists/Reports

[#1]

Description - Many of my users work their tasks off of custom lists/reports/dashboards and not the Worklist. Currently delegated tasks do not pull into any sort of task/assignment reports, so I fear that if tasks are delegated to a user working off such a list, the tasks may fall off their radar as they don't pull in where their other assigned tasks do. 

Why is this feature important to you - Need this to fully utilize the task delegation feature.

How would you like the feature to work - Fields would exist on task reports where you could pull in "tasks delegated to..." and it would reference user ID object. This would allow you to chose if you want delegated tasks to appear in a list or not. Even if they were a separate object report that would be ok! Just need some way to pull a them into a list.

PS this is also an issue with personal tasks, reoccurring tasks, along with these delegated tasks. Though these are called "tasks" they don't pull into reports or show on the workload balancer. Meaning that we really cannot utilize these features as we otherwise would.

Current Behavior - Delegated tasks do not function like regular tasks. You cannot pull a report of delegated tasks and they don't show in the workload balancer.

[#2]

Thank you for sharing this insight. We understand the importance of having delegated work integrated seamlessly into task reports and the workload balancer for effective task and resource management. We’re prioritizing these improvements and will be exploring solutions in our 2025 roadmap.

[#3]

This is currently possible through an Assignment report by leveraging an EXISTS filter to connect the assignment record to the delegated to user through the many relationships that separate an assignment to a delegated user.

After creating an assignment report, I recommend adding the following columns to confirm it is working for you. You can refine the columns to meet the specific reporting output you have in mind as well.
Task Name

linkedname=task
namekey=view.relatedcolumn
namekeyargkey.0=task
namekeyargkey.1=name
querysort=task:name
valuefield=task:name
valueformat=HTML

Delegated User

name=Delegated User
querysort=assignedTo:delegationTo:toUser:name
valuefield=assignedTo:delegationTo:toUser:name
valueformat=HTML

Delegation Start Date

name=Delegation Start Date
querysort=assignedTo:delegationTo:startDate
valuefield=assignedTo:delegationTo:startDate
valueformat=atDate

Delegation End Date

name=Delegation End Date
querysort=assignedTo:delegationTo:endDate
valuefield=assignedTo:delegationTo:endDate
valueformat=atDate

Use the following example EXISTS filter to pull in task and issue assignments that belong to "me" (the logged in user) and that are delegated to me:

EXISTS:A:$$OBJCODE=USER
EXISTS:A:delegationTo:toUserID=$$USER.ID
EXISTS:A:ID=FIELD:assignedToID
OR:1:assignedToID=$$USER.ID
OR:1:project:status=CUR
OR:1:status=DN
OR:1:status_Mod=ne
project:status=CUR
status=DN
status_Mod=ne

The filter above also only displays assignments that are incomplete and that belong to a current project. It could be adapted to focus the results on a specific date range, to show just task or just issue assignments, or any other criteria.

Note; while this same type of filter could be used on a Task report, it is not recommended. From a Task report, you would either be limited at looking at assignments for the primary assigned user through the `assignedToID` or you would have to use the `assignments` collection. Using the assignments collection in combination with an EXISTS filter is not recommended because it will significantly increase the time to load the report, even if there are only a handful of task records to display.

For more information about EXISTS filtering, please review the Create complex Text Mode filters using EXISTS statements article.