this may be too fiddly but have you considered saving as a PDF and then converting the PDF to an excel? Otherwise, I would ping Doug Den Hoed.

Pure conjecture, but I think historically, it's based around Workfront's perception of what counts as "work".   If all you want to do is have someone look at something, why would/should this Reviewer-assigned stuff be counted?   It's not necessarily a philosophy that I support, and if I happen to be...

Are you on the task landing page and logged in as the user? If you still cannot see it from there, just submit a helpdesk ticket and ask for help.

hi, have you experimented with the functionality in a single task? For example, how would you feel about assigning each team member to their own task, and having them add sub-tasks to these tasks?   By the way, I did notice you marked the wrong response as "correct answer," so in the interest of not...

sounds like you’re sharing with each user by name. Would you consider putting them all on a team and sharing with the team name instead?

A task report filtering on Assignment Users / Home Group ID = $$USER.homeGroupID would show you tasks that are assigned to any user in the viewer's home group.   In your case, if teamMember1, 3, 4, 6 and 8 are all in the same HOME group (subTestGroup1), and have permissions to see each other's tasks...

Can you let us know what the sharing policy on your project is? [what does it say when you click on the More options (three circles next to your project name) and "Sharing"?]

Workfront doesn't currently report on Reviewer-assigned proofs, so this isn't going to be possible.

not at the moment, unless you have fusion and are willing to automate. If you don't or aren't, you would need to create a third team (team A+B) and set up three queue topics and three routine rules, one for each team.

LOL I think you have misunderstood (or I may have misunderstood what you're thinking)? This will reset YOUR user preferences back to default settings. Specifically, the user you are logged in as.   It will not affect multiple users. Hopefully that was the misunderstanding!!