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.
Hello Atlassian Community! My name is Ada , and I'm the Product Marketing Manager for Confluence Server at Atlassian. If you missed our last post, we're transitioning to quarterly updates&nb...
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