Question asked during the August 30th, 2012 webinar titled "Improving Processes with Scrum and Kanban"
You can also break add the subticket to the release and close that and then move the user story across to the next release. You wont get point associated since you didn't finish the story but you shouldn't
The rapid board does not provide an auto means of doing this.
A suggested process would be to clone the story in JIRA and edit the clone for the remaining work. If the Product Owner prioritised this work was to be continued, this would then be sized and estimated in sprint planning.
If you clone the stoiry there is an otpion to copy the sub tatsk as well. This can be useful if there are a lot of unclosed sub tasks but it means you have to delete the suib tasks on the original story. The other option is not to clone thje sub tasks but move / reparent them to the new story.
The story would then be moved from your backlog to the next sprint board as normal.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.