The meaning of user story is work that will be compeleted in one sprint.so if its subtasks wont be compeleted in the current sprint u must take the story back to backlog and use it in futur sprints but if u must use it in the current sprint based on priority, u must consider the story as epic cuz more than one sprint takes time.
What problem are you trying to solve by having a story with sub-tasks that are worked on in different sprints?
For example, when there are dependencies between teams on a shared work item, consider instead making independent stories to manage the separate work...and each of those could be completed in specific sprints.
Or as another example, when a single team's work has implementation pieces (sub-tasks) that cannot occur in one time-boxed sprint, consider just making the pieces separate stories....and...consider how in the future the team could split the work into self-contained and valuable stories instead of "technical stories".
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events