Hi @kalyaani
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".
Best regards,
Bill
Hii kalyani
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.
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sub-tasks inherit the sprints from the parent. So you cannot change the sprint on a sub-task. If you know that the sub-tasks in the userstory won't be completed in the a sprint, you should probably consider splitting the story to a more granular level.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.