You can (and usually should if you have complex stories that different people need to do bits of it separately) split a story up into sub-tasks.
But sub-tasks belong to their parent stories. And sprints contain stories. So a sub-task belongs to a story which is dealt with in a sprint, and not the next one.
So, if you have sub-tasks to do in separate sprints, they drag the story with them. A sprint will contain the story, so sprint #1 will have the task and five sub-tasks. If you deal with the first two sub-tasks, then close the sprint, then the task and all five sub-tasks will go to sprint 2 (albeit with 2 closed sub-tasks).
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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