Thanks for taking the time guys, and I understand. As much as I agree that our workflow is flawed by both of your points btrahan and want to applaud you guys at phacility for your median diff size, but our team has a long way to go before we can consider those as solutions. We may try starting a rotation, but if "Bill" is tied to an important story I don't want him context switching every time a diff comes out on Tuesday and dropping the ball on his story. I think we will try just adding a comment to the diff just to state that that reviewer is actively working on the diff, and maybe I'll set up Aphlict and see if that will alleviate some of the pain. But again, thanks for reviewing.

I looked into using Herald but didn't see any Condition that would satisfy the need. Can aphlict notify that someone has viewed the diff or only if someone starts to add comments and such?

Agreed, I'm sure all organizations have different workflows and can see how this may be confusing in some of them. In our case we are a very small team and having multiple people review a diff definitely can affect our velocity. I'll give you an example of our workflow (if you an idea on how to improve our workflow that is also welcomed) and why this would be a wanted feature: