Issue Summary

When the Task Report macro is configured with Sort by: Assignee (or when clicking the Assignee column header to toggle ascending/descending order), tasks are not ordered by assignee display name. Tasks assigned to the same user are not grouped together and appear mixed with other users' tasks.

Instead of ordering by the assignee's alphabetical name, the sort order appears to default to the source page creation/discovery order (Task Appears on).

This behavior was previously tracked in CONFCLOUD-67965 (closed as Cannot Reproduce) and CONFCLOUD-68114 (closed as Duplicate). It is now consistently reproducible

Steps to Reproduce

1. On one or more pages, create multiple inline action items/tasks assigned across at least 3–4 different users (including multiple tasks assigned to the same user, some unassigned tasks, and tasks with due dates).
2. On another page, insert a Task Report macro configured with:

Scope: Space or specific pages containing the tasks
Sort by: Assignee
Reverse sort / Sort order: Test both ascending and descending

1. Publish and view the page.
2. (Optional) Click the Assignee column header on the rendered table to toggle sort order.

Expected Results

• Tasks are ordered alphabetically (A–Z or Z–A) by the Assignee's display name.
• All tasks assigned to the same user are grouped together in consecutive rows.
• Unassigned tasks are grouped together consistently at the beginning or end of the table.

Actual Results

Tasks are not ordered or grouped by assignee:

• Tasks assigned to the same user are scattered across separate rows (e.g., in testing, one user's 3 tasks appeared at rows 6, 7, and 20 on the first results page, separated by other users' tasks).
• Names do not follow alphabetical order in either ascending or descending sort (e.g., initial row sequence: A, D, V, S, R...).
• Unassigned tasks appear scattered in the middle of the table rather than grouped at the start or end.
• The order appears to follow the source page where the task originates (Task Appears on) rather than the assignee attribute.

The issue affects both active and deactivated users.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available