The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
Displaying Backlog with multiple open sprints and future sprints takes a very long time
Bertrand Delaitre
November 30, 2021 edited
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
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
DEPLOYMENT TYPE
SERVERVERSION
7.13.8Community showcase
Atlassian Community Events
Copyright © 2026 Atlassian