Summary

When you open a sprint report, the report data doesn't load, and an internal server error pop-up appears. This can be caused by a board filter querying too many issues simultaneously.

Check for a complex JQL board filter

When a board filter attempts to load more than 5000 issues, this causes the board itself, and all reports on that board, to load slowly or even time out.

The same slow performance can be caused by a complex board filter. Take this filter as an example:

project = ABC AND Team in (12345) OR component in ("ABC component") ORDER BY Rank ASC 

This is a complex filter because the OR component statement is not attached to any specific project. Therefore, Jira will search for issues in all projects that may have this component set.

Remove complexity from JQL filter

We can modify our board filter to limit the results to a single project by adding a set of parenthesis:

project = ABC AND (Team in (12345) OR component in ("ABC component")) ORDER BY Rank ASC

Now, all of our results must come from the ABC project. This prevents Jira from searching all projects, which will improve board performance and allow the sprint report to load.

If you're still seeing internal server errors on sprint reports but have ensured your board filter is not complex, please contact Atlassian support.