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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can't connect to existing filters, boards or project

Hi guys,

We're using a server Jira.

I have trouble with the second step in creating a new plan.

When I'm choosing one of the existing Agile boards or any filters to connect them to the plan, the continuing loader appears.

The one successful attempt happened with the small project. Another one doesn't work. I assume because of the project size. It includes more than 5K issues. 

Please advise. 



2 answers

2 accepted

0 votes
Answer accepted

@Yevhen Onyshchuk - In AR the default issues limit for a plan is 5000.  If you need to increase it because business needs, then you need to enabled the ability (darkfeature) which allow your Jira Admin to bump up the limit via the AR admin UI.  

I would suggest you to contact Atlassian Support on enabling that ability.  However, you should always fine tune your filter query used on a board (used in your plan's issue source) as a best practice.

Best, Joseph Chung Yin

Jira Functional Lead, Global Infrastructure Apps Team

Viasat Inc.

Thanks, Joseph. The issue with the number limits is clear fo me. However, I can't even add the simplest filter or board as a plan source where only one issue type was selected. The reason is the same - a permanent loader (screenshot)Screenshot.png

0 votes
Answer accepted

Hi Yevhen,

This can happen for a number of reasons. You server may not have enough resources for the issues in the project or the number of issues returned by the filter. A lot more occurs in the background when viewing issues in a filter through Roadmaps than just viewing the same filter in the Issue Navigator. You may want to contact Atlassian Support for further assistance. Cheers!

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events