Hi, I have configured following hierarchy in Releeses tab: Release -> subRelease ---> Iteration When I execute one testcase = create test run for the Iteration, I'm not able to populate the test results up to root parent which is Release. E.g. in Testcases tab I see just following overview Release NOT RUN -> subRelease FAULT ---> Iteration FAULT I was wondering why the overall result of release is "NOT RUN"?. I have made sure the testcase are mapped to both releases and iteration. In Spiratest forum, I have found out this related thread, with such statement: https://www.inflectra.com/Support/Forum/spiratest/issues-questions/81.aspx > 31. Octobber 2011 > Currently the test results will only roll-up from Sprint to Parent Release. They don't roll-up from sub-release to parent release. This was originally by design because releases were considered separate from a test results perspective. However based on feedback from customers > we're planning on making this configurable. Is there an already solution for this issue? I'm facing a consideration of designing/mapping of our Release/Iteration/Build hierarchy to allow scalable test result filter. I would probably don't use subRelease if there is such roll up limitation. I would not make sense Than you, Josef 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/spiratest/issues-questions/1417.aspxthreadId=1417Josef Vopicka (josef.vopicka@siemens.com)releases Hi, I have configured following hierarchy in Releeses tab: Release -> subRelease ---> Iteration When I execute one testcase = create test run for the Iteration, I'm not able to populate the test results up to root parent which is Release. E.g. in Testcases tab I see just following overview Release NOT RUN -> subRelease FAULT ---> Iteration FAULT I was wondering why the overall result of release is "NOT RUN"?. I have made sure the testcase are mapped to both releases and iteration. In Spiratest forum, I have found out this related thread, with such statement: https://www.inflectra.com/Support/Forum/spiratest/issues-questions/81.aspx > 31. Octobber 2011 > Currently the test results will only roll-up from Sprint to Parent Release. They don't roll-up from sub-release to parent release. This was originally by design because releases were considered separate from a test results perspective. However based on feedback from customers > we're planning on making this configurable. Is there an already solution for this issue? I'm facing a consideration of designing/mapping of our Release/Iteration/Build hierarchy to allow scalable test result filter. I would probably don't use subRelease if there is such roll up limitation. I would not make sense Than you, Josef Fri, 18 Mar 2016 11:37:07 -04002024-07-17T18:30:48-04:00/Support/Forum/spiratest/issues-questions/1417.aspxmessageId=2577Inflectra Sarah (donotreply6@kronodesk.net) Hi Josef If you look at our recent blog entry on SpiraTest v5.0 - Releases that Roll U p, you will see that v4.2 doesn't have support for the Release > Sub-Release > Iteration reporting that you are looking for, but that it is part of our v5.0 release coming up. Regards Sarah Fri, 18 Mar 2016 14:35:50 -04002016-03-18T14:35:50-04:00/Support/Forum/spiratest/issues-questions/1417.aspx#reply2577messageId=2580Josef Vopicka (josef.vopicka@siemens.com) Hi Sarah, Thank you for your quick and kind answer. It is nice to hear that heal is upcoming. Do you have a rough expectation when the version 5 comes out? In a month, half a year, 1 year? In case I prepare my release structure as Release > Sub-Release > Iteration already today, will I be able to keep my work and migrate my V4.2 project to V5 in order to benefit from the Release Roll up feature? Josef Mon, 21 Mar 2016 12:27:41 -04002016-03-21T12:27:41-04:00/Support/Forum/spiratest/issues-questions/1417.aspx#reply2580messageId=6830David J (adam.sandman+support@inflectra.com) For those reading the thread, this was included in Spira v5.0 and has been in any version after that. Wed, 17 Jul 2024 18:30:48 -04002024-07-17T18:30:48-04:00/Support/Forum/spiratest/issues-questions/1417.aspx#reply6830