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!


Portfolio Plugin Performance Problems


we are introducing the Scaled Agile Framework within our company, therefor we want to create Program and PI roadmaps. We are facing quit some performance issues: stuttering scrolling, slow loading and error messages when loading around 10.000 issues.

Are we using it wrong? Maybe it's not suitable for loading more than let's say 5000 issues? We use AWS, maybe our specs are to low? 

Anyone else having similar problems? How many issues do you load and what are your server specs?

Thanks a lot!




We are running with less than 2500 total issues and we began seeing general performance problems within Portfolio a few days back.   We are running a server instance.

Initial refreshes began to slow from 1-2 sec to 5-6, then finally hitting timeouts.   Commits have been taking longer with the last batch taking around 1-sec per change committed.

I am working with some local admins to track general performance on the server side and Atlassian support directly will not be far behind.


Did you come up with any solutions for improving performance of Jira with Portfolio? Is Atlassian support tracking performance problems in tickets? If so, can you provide the ticket ref here please?

We too are leveraging Scaled Agile and see performance issues for plans that include a significantly large number of issues ( > 10,000).  As some of the recommendations with JIRA Issue Filters indicate, anything you can do to reduce the volume of data coming back from a JQL query will help, but we've still hit limits.  One thing we found that did seem to help was using a program and then pulling in smaller plans.  That is, if we had a plan that had 30,000 records, we could instead create three plans chopping it up into a relevant category/business unit, and then creating a Portfolio "Program" that read in the three plans. I'm not quite sure why, but it just seems to perform better.

That said we're not out of the woods, and as with other posters here would be interested to hear what other's have found.


Log in or Sign up to comment