Inflectra Customer Forums: How can i filter defects across more than one Release? (Thread) I need to review and prioritise Incidents that have been raised from multiple Releases. However, the filtering is limited to a single release. Is there any other way I can achieve what I need? I find it quite surprising (and frustrating!) the filtering is so limited within the Incidents module. 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/3047.aspxthreadId=3047Luke Cheater (luke.cheater@computacenter.com)How can i filter defects across more than one Release? I need to review and prioritise Incidents that have been raised from multiple Releases. However, the filtering is limited to a single release. Is there any other way I can achieve what I need? I find it quite surprising (and frustrating!) the filtering is so limited within the Incidents module. Thu, 19 Jun 2025 08:11:54 -04002025-09-30T11:15:51-04:00/Support/Forum/spiratest/issues-questions/3047.aspxmessageId=7307David J (adam.sandman+support@inflectra.com) Hi Luke Part of the reason is the filtering is hierarchical, so filtering by a release includes al Hi Luke Part of the reason is the filtering is hierarchical, so filtering by a release includes all child Sprints/Phases. We have been looking into ways to improve this that dont break that paradigm. So its something in our backlog, but I dont have a specific ETA. Regards David Fri, 27 Jun 2025 14:22:25 -04002025-06-27T14:22:25-04:00/Support/Forum/spiratest/issues-questions/3047.aspx#reply7307messageId=7365John Ross (John217Ross@www-ezpasspa.com) The limited filtering youre experiencing is common in many incident management tools. The best way The limited filtering youre experiencing is common in many incident management tools. The best way to review and prioritize incidents from multiple releases is to use the platforms advanced search or query language (like JQL in Jira). You can create a query that filters for multiple releases simultaneously, such as (Release = Release_A OR Release = Release_B). Alternatively, you can create a custom dashboard or report to pull in data from various releases, or simply export the incident data to a spreadsheet to analyze it with more powerful sorting and filtering tools. Tue, 26 Aug 2025 08:24:32 -04002025-08-26T09:45:19-04:00/Support/Forum/spiratest/issues-questions/3047.aspx#reply7365messageId=7398Victoria D (nino.diasamidze@inflectra.com) Hello, There is an existing enhancement about that in our internal system so to add ability to fi Hello, There is an existing enhancement about that in our internal system so to add ability to filter by multiple releases on list pages. However, you can get the filtered list using additional functionality: - Using custom reports - Select all unfiltered data on the list page, then Tools -> Export to Excel - Using Excel365 addin - With OData (if using SpiraPlan) or any compatible 3rd party app with OData feed support Regards, Victoria - Tue, 30 Sep 2025 11:15:51 -04002025-09-30T11:15:51-04:00/Support/Forum/spiratest/issues-questions/3047.aspx#reply7398