What is the best practice to handle parent ticket with multiple sub-tasks?
I suspect that there will be multiple approaches depending on the company processes and procedures for their release cycle.
I am trying to put together a process for handling parent tickets that have multiple sub-tasks for each release cycle. However, I find that there are multiple scenarios and pros/cons.
Here is my question:
1. What should be done when a parent ticket has partially completed sub-tasks?
- e.g. 2 out of 3 sub-tasks have completed in the release cycle
- should the parent ticket left open and move to the next Sprint?
2. Should we close the parent ticket and create a new one with the open sub-tasks?
- PLM team needs to track the original story/parent ticket. By closing and recreate a new parent ticket causes a confusion and ambiguity of the story delivery.
3. What should we do with the completed sub-tasks and left over open sub-tasks?
- How should these sub-tasks be tracked for Sprint cycle/s?
There is a suggestion at our company to not close the parent ticket until all sub-tasks are completed/closed. My concerns with this approach are:
1. It will cause the confusion in the Sprint board/report as it doesn't show the sub-tasks.
2. Should we automatically move the incomplete parent ticket to the next sprint? How does JIRA track the time tracking for this parent ticket?
I would appreciate if you could share your thoughts on handling this situation.
Teams do amazing things together. We’ve talked about the myth of the lone genius and how everything is actually the result of teamwork. You might be thinking, What about a novelist writing, say, Th...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs