Issue limit in Portfolio ?

We have a SAFe programme running which has been set up using individual projects per scrum team, with a hierarchy of Capability > Feature > Story.  We're using Epics to represent Features.  Capability is a new issue type in JIRA.  Portfolio recgnises the hierarchy and this part works fine.

We have about 10 projects and have just completed planning for our first Programme Increment.  If I report on all epics and stories, the total number across the portfolio is over 2000.

Having added the projects into Portfolio, I've found that we can't drill down to user story level as Portfolio reports "The next level of hierarchy is currently disabled. There are too many issues to load them all individually. Please use the filters to narrow down the data set first"

This seems to be quite a major limitation as surely the idea of Portfolio is to bring all of the data together, and we've hit the limitation already in our first sprint! 

Questions are: What is the actual limit?  Any tips on getting around this?  Is this configurable? Surely there is not an expectation that stories are not viewed at Portfolio level?

 

Thanks

 

 

1 answer

Hi Harvey,

Take a look at the Communities post How to confirm/limit the number of issues into Portfolio for a bit more information.  In addition Live Plans set a hard loading limit.  The current default is 2000 issues.

As you start having more and more issues in your plan, interacting with Portfolio becomes slower.

JIRA Portfolio tries to load all the issues which match the current filter. If it sees that a certain hierarchy level has too many issues, it will disable that level.

The best way to work around this would be to apply a filter on something the issues have in common, such as the project or release. This will reduce the total number of tasks allowing epics to be expanded.

At this point, you can use filters narrow down the issues they want to work with and this will allow you be able to expand the epics.

Workaround

It is possible to change this value in Server. Though it should be noted that this can cause the UI to become slow and unresponsive. We won't be able to guarantee a seamless operation.

The instructions to change the limit are as follows:

  1. Enable the "com.atlassian.portfolio.limits.LoadingLimitsConfigurability" dark feature
  2. Go to /secure/PortfolioLoadingLimits.jspa
  3. Modify the "Hierarchy issue limit"
  4. Refresh the plan page

Hopefully this helps.

Cheers,

Branden

Roi Fine Atlassian Team Jan 09, 2018

A description to the doc that describes the plan limitations can be found here: https://confluence.atlassian.com/jiraportfolioserver/creating-and-deleting-plans-802170502.html

Suggest an answer

Log in or Join to answer
Community showcase
Josh Frank
Posted Dec 01, 2017 in Portfolio for Jira

Portfolio for Jira: Share your tips!

The Portfolio for Jira team wants to hear from you. Share your top tips for building a great Portfolio for Jira plan for a chance to win some Atlassian swag.  Do you structure your teams i...

543 views 6 8
Join discussion

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