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!!

hi, since you already recognize this is not on the project level, you can go to the API explorer and use the References section -- this will show you all the areas you can reference (especially if you switch to the unsupported version of the API). The object you are trying to reference is the conver...

yes!! That's exactly the one I was thinking of. I think I used to use it to run word searches 

The only other thing I can suggest is, depending on the proof you can export it as a PDF with PDF markups (and then reupload it to Workfront). You won't be able to look at it in the same way you look at a regular Proof, but at least the comments will come over intact.  

sorry for the misunderstanding, Surya -- your calculated field syntax is otherwise correct (and M's is old and outdated). M would want to use your syntax and add the IF/ISBLANK to it in order to cover all the based: i.e. a working calculation that doesn't overwrite itself.

I would tend to disagree. If I don't miss my guess, a queue topic and topic group name can change when they get accidentally or purposefully deleted. Coding in an isblank would protect against this risk.