Hi, We have a suite of custom reports that rely on the Release control in the custom section filter to work which has been working great (once I learnt about the ${ReleaseAndChildIds} token anyway). However, recently weve started marking releases as Closed to prevent QA from accidentally executing against old releases but this seems to result in the closed releases not being selectable in the reporting filters. So my questions are: Are closed releases being deliberately filtered out of report filtering functionality? If this is a bug what are the chances of a fix? Is there a work around? (One that ideally that doesnt involve reopening any release artifacts we want to report on, or even worse, having to hard code requirement IDs to report on historical releases) Any guidance would be appreciated. Regards, Brad. 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/2865.aspxthreadId=2865Brad Straka (bstraka@stayinfront.com)custom reports Hi, We have a suite of custom reports that rely on the Release control in the custom section filter to work which has been working great (once I learnt about the ${ReleaseAndChildIds} token anyway). However, recently weve started marking releases as Closed to prevent QA from accidentally executing against old releases but this seems to result in the closed releases not being selectable in the reporting filters. So my questions are: Are closed releases being deliberately filtered out of report filtering functionality? If this is a bug what are the chances of a fix? Is there a work around? (One that ideally that doesnt involve reopening any release artifacts we want to report on, or even worse, having to hard code requirement IDs to report on historical releases) Any guidance would be appreciated. Regards, Brad. Sun, 29 Oct 2023 23:09:02 -04002023-10-30T18:44:44-04:00/Support/Forum/spirateam/issues-questions/2865.aspxmessageId=6216David J (adam.sandman+support@inflectra.com) Thanks for your questions: Yes that is correct, so they dont clutter up the filters, that is by design N/A You could try leaving the Releases as Completed vs. Closed. Im afraid Im not sure of other options. Id log a support ticket to get additional guidance - https://www.inflectra.com/Support/Ticket/List.aspx Mon, 30 Oct 2023 00:45:21 -04002023-10-30T00:45:21-04:00/Support/Forum/spirateam/issues-questions/2865.aspx#reply6216messageId=6217Brad Straka (bstraka@stayinfront.com) Thanks for the quick response David. I did try using Completed and while that locks down the release form, it wont stop QA assigning new runs against that release which is what we are trying to prevent. Ill have a chat with the powers that be here in the office and see if we want to go down the ticket route. Regards, Brad. Mon, 30 Oct 2023 18:44:44 -04002023-10-30T18:44:44-04:00/Support/Forum/spirateam/issues-questions/2865.aspx#reply6217