Release Summary Report Seems Inaccurate

Wednesday, May 22, 2013
I ran a release summary report and under our week one iteration it says that there are 0% of the tasks not started.  However I go into a requirement that is associated to that iteration and there are many tasks that say not started.
1 Replies
Thursday, May 23, 2013
re: swycoff Wednesday, May 22, 2013

In general if the tasks don't have any effort value (i.e. are zero hours) they will not get counted towards the requirement or release/iteration totals since we weight the values by effort.

If that doesn't explain the issue, could you submit a help desk ticket with some screenshots, that way we can better assist you?



  • Started: Wednesday, May 22, 2013
  • Last Reply: Thursday, May 23, 2013
  • Replies: 1
  • Views: 2163