Hi Phil - thank you for making the attempt to build a report.
The way my workflow operates is simply people assign tasks to me for investigation/action. I’m not part of any broader discussion on the scheduling or prioritisation of tasks. Some tasks I will action and complete. Some I will comment on, mentioning someone else to ask for their input and then wait to see their comment added in reply before I act on them again. Some I will assign to others - in some cases expecting they will be assigned back to me later once some item of work is done; in other cases not expecting the task to come back to me. For any of a number of reasons I might want to go back and re-read a task I have “touched” in this way - to double-check some information; to view a screenshot that was embedded in the task or comments; to review a file attachment that was added to a task.
As an analogue, I write a lot of SQL for database queries and database fixes. I save these into a folder. While the file name encodes useful information about each file (such as a ticket number or description of the function of the file), I typically have my File Explorer window open showing Details view and sorted by date last modified, descending - which means the most recent files I have worked on sit at the top of the list - regardless of their chronological ticket numbers (which are at the start of the filename).
What I have found in Asana is that once a task is no longer assigned to me it is difficult for me to locate it. It may have been in one of any number of projects. I either have to scroll through the inbox in hope of finding recent communications about the task (and as mentioned, the format of that stream of information is not conducive to visually scanning) or use search and hope I recall keywords in the task.