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

getting a "Too many issues" error when setting up sources for a new plan

Error - Your current selection includes too many issues to load correctly. Refine your selection to connect to fewer releases or projects.


We have 6-8 projects with 2-3 releases each that I had been using as sources for a Portfolio Plan.  I'm trying to create a new plan for the next year and am getting this error.  


Anyone had this problem?  Is it the result of a new release?  Is there a numeric limit of issues?




1 answer

1 vote

Hi Bryan,

This is because the number of issues you have selected may have exceeded some system limits. You can refer to the documentation links given below to understand various limits applied while creating a plan.

If you are using version above 3.0,

If you are using live plans (2.0 to 2.27),

Let us know if you still face any difficulties after fixing the limits.


Portfolio for Jira Team 

Hi, I'm no where near exceeding the issue limit.  Its confusing because this used to work fine, and I'm not sure exactly when it broke.

The new plan I'm creating includes 7 projects, with 1 or 2 fix versions selected per.

The number of total issues is under 1000:

project a - 38

project b - 339

project c - 80

project d - 311

project e - 9

project f - 117

project g - 18

total - 918 issues


I look forward to your thoughts.  


Are you including sub-tasks in the count? I ran into the same issue (800 issues), but when include sub-tasks I'm at 5,179.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events