How can i filter defects across more than one Release?

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 don't break that paradigm. So it's something in our backlog, but I don't have a specific ETA.

Regards

David

The limited filtering you're experiencing is common in many incident management tools. The best way to review and prioritize incidents from multiple releases is to use the platform's 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. 

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 -