Too many issues are trying to load

[Shashi K]

Hello Jira Team,

We are facing strange issue while we are accessing the board/backlog. We are unable to see the tickets which we had created in Sprints as well as in Backlogs. It shows below icon and where if I click on update Update filter it just landed in Settings and no where I see setting to update the count of tickets

.  

[Nic Brough _Adaptavist_ · Accepted solution]

When you click update filter, is should take you to the issue navigator where you can adjust the filter so that it doesn't try to include too many issues.  What does the filter show you?  There's a summary count on the issue navigator page.

[Shashi K]

When I click on "Update board filter" it navigated me to "General and filter"

Where I see below options 

[Nic Brough _Adaptavist_]

When you click "edit filter query", it should take you to the issue navigator which shows you a paginated list of the issues.  At the top of that, it'll tell you how many there are.

[Shashi K]

Are you talking about this ? It shows 1000+, what should I change to to view things in Backlog, I m not even able to see Start Sprint :(. We are stuck. 

[Shashi K]

Any update ?

[Nic Brough _Adaptavist_]

Could you try editing the filter so that it returns fewer issues?  Ideally less than 1,000

[Shashi K]

This is resolved, would like add more points to Nic,

- When you click on "Edit filter" 

- Try a filter with the Date ranges will will reduce the count. 

- Save filter as "Name of the filter "

- Then pick the saved filter in "Saved Filter" category. 

- In my case "WE board filter" is default, dropdown will show you the saved filter.

- Pick that and go to your board this should bring back the board.

Thanks 

[Karen M. Smith]

Do you follow the same for NextGen?

[Yatish Madhav]

Hi - is this some sort of new issue today? We added a new project category in the board query filter to include issues from a reordered set/category of projects and then got the "Too many issues are trying to load" error on the Backlog page under all the Sprints. On reverting it back, it stayed the same. Yes, we had and have over 1000+ issues found but why is this appearing now even on reverting the filter? Please advise?

[Nic Brough _Adaptavist_]

My guess would be browser caching.  Check that the current filter returns less than 500ish (open) issues, then try closing the browser and re-starting it.

[Karen M. Smith]

How do you change this in NextGen?

[Nic Brough _Adaptavist_]

Do not put too many issues into a sprint.