Hello, My current team uses SpiraTeam as follows: Release - Iteration 1 - Iteration 2 - Iteration 3 - ... I have PM's complaining if we map requirements/incidents/tasks to the iterations, they will not roll up to the Release. For example, to see all work done in Iteration 1/2/3 we have to go directly to those iterations rather than go to the release where they expect to be able to see everything the team has done to get that release out the door. Is this true? Do work items that are completed in a specific iteration not roll up to the release? If it is incorrect, where should we go to see that roll up? 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/issues-questions/663.aspxthreadId=663Tonja Davis (tonja.davis@wizards.com) Hello, My current team uses SpiraTeam as follows: Release - Iteration 1 - Iteration 2 - Iteration 3 - ... I have PM's complaining if we map requirements/incidents/tasks to the iterations, they will not roll up to the Release. For example, to see all work done in Iteration 1/2/3 we have to go directly to those iterations rather than go to the release where they expect to be able to see everything the team has done to get that release out the door. Is this true? Do work items that are completed in a specific iteration not roll up to the release? If it is incorrect, where should we go to see that roll up? Wed, 31 Jul 2013 20:06:33 -04002013-08-01T18:02:07-04:00/Support/Forum/spirateam/issues-questions/663.aspxmessageId=1212David J (adam.sandman+support@inflectra.com) Hi Tonya If you assign requirements, tasks, incidents, etc. to an iteration, it should also be considered part of the parent release and the effort values will all roll-up. Regards Adam Thu, 01 Aug 2013 18:02:07 -04002013-08-01T18:02:07-04:00/Support/Forum/spirateam/issues-questions/663.aspx#reply1212