You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi,
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!
Best,
Daniel
Hi,
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.