I have a Jira Plan to track a cross-team initiative.
My issue sources are selected from two routes:
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?
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events