Hi, here's our sprint planning use case.
While decomping stories into sub-tasks, the engineers will find a story is too big for the sprint and must be made into 2 parts.
PMs will clone the story and title it appropriately.
But the original story has sub-tasks that should be moved into the 2nd story.
What is the best way to accomlish this easily?
There's got to be a better way than clicking into sub-task, clicking move, "change Parent". Which wouldn't be that bad if you can select sub-tasks in "Plan" mode.
I agree there should be a better way than having to individual move each sub task.
I opened an issue for improving this when bulk moving a number of sub tasks but unfortunately Atlassian did not see it as important and closed it this September saying:
I understand that it's frustrating to see an issue closed that you want implemented, especially when it's acknowledged as a good suggestion. The JIRA PM team has decided to close any issues that we know will not be on our roadmap in the next 12-24 months. We want to be as honest as we can, and not lure you into a false sense that we may fix it soon.
How ironic...I just received this same question today. An item was broken down into different tasks and they have to individual change parent on 20 subtasks. The were confirming that they had to do each one-by-one vs using the bulk move capability.
Closing an item vs allowing individuals to vote on an item seems an odd practice. I wonder why they have improvements out there for 5+ years with 100's of votes still open..they obviously didn't plan to put it on their 12-24 month roadmap if it's been open for that long! (using their logic)
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot