Parent user story with multiple tasks and subtasks

Farrukh Siddiqui

Who should the parent story assigned to when there are multiple child tasks or subtasks of that story in different states like In Dev, In QA and assigned to different users. and what should be the overall state of parent story when child tasks are in different states?

Nic Brough -Adaptavist-

The assignee should be the person responsible for getting the issue dealt with, the single point of contact for it.  This does not necessarily have to be the person who is going to actually fix/code/deal with it, especially if it's broken up into sub-tasks which could be assigned to other people it's just the single person who is ultimately responsible for it.

On the status, that's up to your process.  You should not let an issue with open sub-tasks go into a "done" status, because by definition, it is not done if parts of it are incomplete (sub-tasks are very much a part of their parent issue), and generally I'd say that if any sub-tasks are in progress then the parent should be in an in-progress status (rather than the "open/new where we haven't looked at it yet"), but other than those two broad rules, I'd say it's not that important and you should be guided by your reporting more than anything else.