Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Migrated from Server to Cloud - Now a few projects are showing "Too Many Issues to Load" error

We are in the process of migrating a bunch of projects from Jira Server to Cloud. In Server my board query might simply be project = "project name" ORDER BY Rank ASC. Over the course of many years, this project has 32,437 issues of which 28,949 are Resolved. My board loads just fine in Jira Cloud with the issues that are still open. I did not have to adjust the query at all. Many other projects we migrated work fine.

I have 3 projects that are giving me the "Too many issues to load..." error. If I run the query in Jira Server, it's the same scenario - many thousands of issues over many years of work and the majority are closed. For some reason these 3 projects seem to be trying to load everything.

I tried re-writing the query so that is would ignore issues that were Done or Won't Fix and part of a closed sprint but it left out issues that were carried to the current sprint and closed there. Bummer.

Has anyone had this experience when migrating? Am I missing a checkbox somewhere? 

1 comment

To close this out in case anyone finds it and needs the same help:

Atlassian recommended: project = "CSP" AND (Status not in (Done, Won't Fix)) OR (Status in (Done, Won't Fix) AND Sprint in openSprints())

We ended up using project = CMM AND issuetype not in subTaskIssueTypes()ORDER BY Rank ASC and it solved our issue.


Log in or Sign up to comment