Using Jira Server 7.13.8.
In one of our projects, we have a backlog that displays 2 current active sprints and 6 future sprints. The associated filter returns less than 100 issues.
Displaying this backlog takes more than 15 seconds.
If we modify the filter to display only active sprints with sprint in (currentsprints()) or to display only future sprints (sprint in (futuresprints()), the display takes less than 3 seconds.
Combining currentsprints() and futuresprints() increases the load time to 15 seconds.
Is this a known behavior?
Can we hope to have better performances with Jira Server 8.13?
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
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