We found that the web UI uses an API endpoint capable of directly returning a paginated list of tasks across all parent record types that is utilized by the native "Task" section. In contrast, the documented public REST API appears to require retrieving each parent record such as a ticket or change, and then making a separate request to determine whether it has any associated tasks. This results in an extremely large number of additional API requests simply to identify tasks across tickets, changes, and other record types that are returned by the original queries.
A supported public endpoint for listing tasks directly would be significantly more efficient and eliminate the need to query every potential parent record individually. Could this functionality be made available through the public REST API? If it is not currently planned, could this request please be submitted as a feature enhancement?
