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! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Migrated from Server to Cloud - Now a few projects are showing "Too Many Issues to Load" error

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

Kelly Bates
June 14, 2021

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 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Kelly Bates
June 16, 2021

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.