Portfolio project limit

We are trying to setup a live plan with about 300 projects but we run into a portfolio imposed limit

 

image2016-6-1 10:42:55.png

 

Your current selection connects to too many projects for the plan to load correctly. Refine your selection to connect to fewer projects.

 

We are using a filter which returns issues from 2 different projects...

 

3 answers

2 votes

Hi,

The maximum amount of projects you can source into your Portfolio plan is 100.

 

Hi Rhys,

Are there any plans to increase these limits?  Large organisations are not going to be able to limit themselves to such a low amount.

Thanks

Ryhs - 

I think there is a bug.  

I have two filters:

Filter A:

"NFIB Boards" = P1 AND Archived is EMPTY AND issuetype in (standardIssueTypes()) AND project not in ("Products - All Other", "Production Processes Product", "netFORUM Custom NFIB-Owned - netFORUM Database", "netFORUM Custom NFIB-Owned - Reports") ORDER BY Rank

Filter B:

"NFIB Boards" = P1 AND Archived is EMPTY AND issuetype not in ("User Story", Sub-task, "Dev Task") ORDER BY Rank ASC

--

Both Filters pull back similar numbers of issue (though not identical), but I have confirmed both have a unique project count of 33.  

JIRA Portfolio tells me too many projects with Filter A.

JIRA Portfolio DOES NOT tell me too many projects with Filter B.

Hi, there definitely is a bug here as I have projects limited to only 4 or 5 projects, and am still getting this error

I have only 36 project loaded, and I need double this to reflect the program.  Please investigate this issue if 100 should be allowed. Several of the projects have 000's of issues.  Could that be the problem?

Hey Mark & Nicole - (unsure why I can't @mention Nicole)

Are you positive you're receiving the project limit warning message?
We also have an issue loading limit of 5000 issues.
More info about that here: https://answers.atlassian.com/questions/39140034

If this you're indeed receiving project limit warnings with much fewer than 100 projects then please create a support request here so we can track and investigate the problem:
https://support.atlassian.com

Thank you

Hi @Rhys Christian, Nicole, @Jason Wyckoff, I did raise a bug for this but it seems we 'fixed' this by specifying the project/s in question.

So it seems the error is not based on the number of projects returned by the query, but by the number of potential projects returned by the query, which might explain why Jason gets the error with filter A and not filter B because the query includes "AND project not in..."

 

I got the same error with a filter that tapped only a single project although the project wasn't specified. When I specified the project, I didn't get the error.

Could the documentation be updated to reflect what's happening when you get this error?

I have the same issue, and would love to know the max number or how it comes with this message.  

 

I have the same issue as well. 

0 vote

Hey Jason - The max number of projects is 100

Suggest an answer

Log in or Join to answer
Community showcase
Emilee Spencer
Published 3 hours ago in Marketplace Apps

Marketplace Spotlight: DeepAffects

Hello Atlassian Community! My name is Emilee, and I’m a Product Marketing Manager for the Marketplace team. Starting with this post, I'm kicking off a monthly series of Spotlights to highlight Ma...

22 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot