Should assignee change whenever a user is requested for informations/actions?

unknown

Greetings all,

 

in my previous company we had always our issues assigned to the person who was responsible for the issue at that specific time , regardless of whether they were being asked for feedback/thought/informations, or they were requested to action the issue.

For example:

1. user A creates the issue, becomes Reporter
2. user B picks up the issue, assings to herself
3. user B finds out they need more informations from user C, assigns the issue to user C
4. user C adds more informations and assign back to user B
5. finally, user B completes the work and assigns back to the reporter.

This can end up being a carousel of assignee changes, but I like it because everyone can see what issues are waiting for them.

Are there other recommended ways to handle this? Any suggested improvements?

TIA!

Liam Green

Hi @[deleted]

I think the B to C and back again makes sense (so long as there are appropriate internal notes from B explaining why they have assigned to C) - the only thing I found a bit odd in your flow was that the issue is then assigned to the reporter?  Would you not just let B mark as resolved?