I have a Jira Plan to track a cross-team initiative.
My issue sources are selected from two routes:
- Two Projects are included, that are wholly supporting the Plan
- One saved filter, which is a query for presence of a `mp-track` label, but the scope of the JQL is narrowed to a select set of projects. Pseudo is `labels = mp-track AND project in(A,B,C...J,K)`
For weeks, the Plan fails to load, or takes ages.
I noticed that as the plan loads, I see 4 years of historical releases indicated on the timeline. These then disappear to load the scope specified in the view.
I followed this guide and excluded 2566 Releases.
My Plan includes 658 issues.
---
When the plan fully loads, those 2566 releases have vanished (correctly), but it seems that the exclusion comes after attempting to compute, rather than up front, causing it to fail to load.
---
The releases that show and then disappear are a mix of Released and Unreleased.
Should my teams be Archiving releases after a period? Would this solve the problem?
