Displaying Backlog with multiple open sprints and future sprints takes a very long time

Bertrand Delaitre November 30, 2021

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?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.13.8
TAGS
AUG Leaders

Atlassian Community Events