Iteration to Release mapping

Wednesday, July 31, 2013

My current team uses SpiraTeam as follows:

- 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?
1 Replies
Thursday, August 1, 2013
re: davist Wednesday, July 31, 2013

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.



Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Wednesday, July 31, 2013
  • Last Reply: Thursday, August 1, 2013
  • Replies: 1
  • Views: 2544