Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Issues & Questi... > Iteration to Release mapp...

Iteration to Release mapping RSS Feed

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
Adam SAdam S
re: Tonja Davis on Wednesday, July 31, 2013
Thursday, August 1, 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.



  • Started: 7/31/2013
  • Last Reply: 8/1/2013
  • Replies: 1
  • Views: 503
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2017 | Licensed to Inflectra Corporation.