What is the best practice for splitting stories? Right now, we have to clone the story twice, then filter all stories and make those two cloned stories children of the split story. There has to be an easier way :) Other agile tools that I have used in the past had an explicit action for splitting stories that really streamlined this process. I am hoping I am just missing something. en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spirateam/best-practices/1748.aspxthreadId=1748Cher Nicastro (Cher.nicastro@ecifm.com)agile story management What is the best practice for splitting stories? Right now, we have to clone the story twice, then filter all stories and make those two cloned stories children of the split story. There has to be an easier way :) Other agile tools that I have used in the past had an explicit action for splitting stories that really streamlined this process. I am hoping I am just missing something. Thu, 28 Sep 2017 17:59:21 -04002017-10-04T15:06:43-04:00/Support/Forum/spirateam/best-practices/1748.aspxmessageId=3121Jim R (donotreply5@kronodesk.net) Hi Cher We have the ability to Split tasks already, so you can have a requirement (user story) with two tasks. We dont have a similar feature for user stories, but it is a good one. Regards Jim Wed, 04 Oct 2017 14:56:11 -04002017-10-04T14:56:11-04:00/Support/Forum/spirateam/best-practices/1748.aspx#reply3121messageId=3123Cher Nicastro (Cher.nicastro@ecifm.com) Thanks Jim. We are already using tasks to define the work that needs to be done to complete the user story. Splitting user stories is a very different thing in Agile. Hopefully SpiraTeam will add more features that are Agile friendly in future releases. Wed, 04 Oct 2017 15:06:43 -04002017-10-04T15:06:43-04:00/Support/Forum/spirateam/best-practices/1748.aspx#reply3123