https://getsupport.atlassian.com/browse/PSSRV-68379

any news about this?

+1

5000 issue limit is pretty much a joke as far as enterprise solutions go. We're not running a lemonade stand here. Please prioritize functional, performance improvements over making a shinier UI.

Any plan to do this soon? With no more jira server we need this feature even more now.

Our company is starting to use Adv Roadmaps for Enterprise level planning and we are hitting these limits.  We've tried limiting by all different methods but we're still running into problems.  I would like to vote this up * 1000 please!

We have in the company projects with more than 5000 issues.

And we need the portfolio to allow more issues in the Plan.

Please add configuration parameters for
maximum issues
maximum project
We need to use Jira Portfolio to have a vision of all running developments and links between dependent projects; hard limit is not an option viable for us

Hi Roi and Atlassian

This is very important for us, since our teams are cross functional each team bring in issues from a lot of Jira projects to there backlog. To get around the "project" limit each team has to have there own portfolio plan and management have to sync and balance workload between teams manually, The team features is just useless.

Please prioritize fixing this,

Carl

Second line on the product page!
"Portfolio for Jira helps you build a plan, see the big picture..." (not that big picture)

Hi Roi,

Happy New Year

I get what you're saying about priorities, however, reporting at the Program level is too limited to allow for the split you recommend.

What are the chances of the Program level getting the same reports currently available at the Portfolio level?

Thanks,

April

Hi All,

Thank you for commenting on this issue with your feedback. I’d like to give you a quick update on this feature improvement. We’re continuously investigating solutions to improve performance, but loading & viewing a very large amount of issues at once is complex. 

The issue & project limits most likely won't be extended in the next few months. The Reason is that we chose to invest most of our effort in simplifying the UI with a brand new design, details can be found here. 

We know that this is a major issue for some of you and longer term ( 12-18 months ) we will  increase our efforts to extend these limits in a way that won’t lower performance.

In the meantime, I would advise customers to split their work streams into different plans. You could use the Programs feature to get an aggregated view of multiple plans, for basic reporting functionality.  

Roi Fine | Product Manager 

This is a MAJOR problem.  Like Cheryl above my query returns only about a dozen results, yet I am prevented from creating a plan with that filter.  In fact, the number of projects with any relationship to the query (i.e., the number mentioned in the query (about 6) and the number of projects returned in the results (about 7) is nowhere near 100.  This needs to be fixed ASAP.  Why are we paying for Portfolio if we can't use it?

Dear Team, is there any update on this issue? We would like to understand how soon we can expect the enhancement. Please advise.

We just started to use Jira Portfolio an just run into this issue! - For each customer we create a customer project with as low as 1 ticket per project. The development scrum board pulls in arround 400 projects, but only 1300 tickets. These are all handlet by the same team I wanted to create a live plan for. Jira Portfolio ist just not flexible enough!

I could easely live if you get rid of the "live" part of the plan and calculate everithing on demand, with creating "calculate" or something. Performance issue should not be an issue then.

Please fix this. It is blocking us from using Portfolio at all. We have 10 teams (boards) and approx 20k issues. We already tried to reduce the amount on the boards, but still... This is not scalable.
At least you could add more intelligent options to the Import Dialog like filtering Version per hierarchy level, etc.

We have a very big solution with multiple teams contributing to it. We already ran into this limit, which is very concerning considering that only about 75% of our teams are onboarded.

Hello, we are currently evaluating Portfolio and have also run across this limitation. Is there a plan to increase the limitation? With the current limitation, Portfolio is not a viable option for us. Thanks

Hello, we have investigated further. There appears to be a bug with the way portfolio is evaluating the filter. I only have access to 12 projects in the total Jira project instance. 

Portfolio shouldn't validate the project count first without considering the entire filter

[‎1/‎22/‎2018 3:09 PM] Keller, Dale (RIS-HBE):

that it should only bring back how many number of projects I have acces to but it's stating there are 692 being brought back

2018-01-22 20:05:27,421 http-nio-8081-exec-139 ERROR *Gil*morcd@Risk 1205x1899435x1 1cnonod 172.23.58.94,0:0:0:0:0:0:0:1 /rest/jpo/1.0/plan/setup/projects [c.a.r.c.r.provider.exception.DefaultExceptionMapper] Encountered number of projects: 692
2018-01-22 20:05:27,420 http-nio-8081-exec-139 WARN *Gil*morcd@Risk 1205x1899435x1 1cnonod 172.23.58.94,0:0:0:0:0:0:0:1 /rest/jpo/1.0/plan/setup/projects [c.a.r.j.c.issuesource.context.DefaultIssueSourceContextService] exceeded project limit (692 > 100) with projects: 

which is incorrect because the entire filter was not considered.

Below is the filter. There are only 26 issues returned.

"Operations Teams" = "Windows - (Dong Lam)" AND status not in (Completed, done, Cancelled, Resolved) AND project not in ("WINDOWS - INFRASTRUCTURE") AND issuetype != Project

Any update on this feature request? Please advise.

Thanks & Regards, Nicole

Just to make sure that JPOSERVER-1958 is not a duplicate really. We are looking at three limitations here:

• 100 projects
• 5000 issues load
• 2000 issues render

This issue here refers to the first two. The one closed as duplicate referes to the rendering limit of 2000.

I think though that it makes more sense to keep all three of them together here.

Totally agree with Peter. 

In Cloud JIRA Portfolio, there appears to be a 1000 issue limit... not really a portfolio... not more than a few teams backlog.

Hey Vicky! Anyone over there have any updates or suggestions for users with this issue?  

I've seen the suggestions mentioned in this answers post, but I wanted to see if there was anything in the works?  As you can imagine, this is a major setback for customers with larger Plans trying to scale up.  Limiting stories and manually entering the aggregate story points for the epic isn't ideal.

When can we expect it to be updated so that can handle at least 500 projects ??