Inflectra Customer Forums: Release Summary Report Seems Inaccurate (Thread)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.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/590.aspxthreadId=590S Wycoff (shelley.wycoff@emeraldconnect.com)Release Summary Report Seems InaccurateI 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.Wed, 22 May 2013 16:47:14 -04002013-05-23T13:43:17-04:00/Support/Forum/spirateam/issues-questions/590.aspxmessageId=1097David J (adam.sandman+support@inflectra.com) In general if the tasks don't have any effort value (i.e. are zero hours) they will not get c 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? Regards Adam Thu, 23 May 2013 13:43:17 -04002013-05-23T13:43:17-04:00/Support/Forum/spirateam/issues-questions/590.aspx#reply1097