We are just starting to use Portfolio and I have it configured to bring over about 10 Initiatives and Epics based on an existing Kanban board. However when I go to load the Schedule view, I get an error saying "This plan contains too many issues to load correction. You need to reduce the number of issues by reconfiguring the plan's sources."
There should only be a handful of issues. Is it also looking at issues in those Epics (eventhough they aren't part of my query / Kanban board)? Does anyone know what the limit is and how you can check the number of issues Portfolio is trying to bring over?
The limit on the amount of issues you can load into your plan is 5000. However there is a hierarchy limit of 2000 which is the limit on the number of items that we are willing to render.
So if your epics (+ initiatives if you use them) are < 2000 then we’re able to show you the epics level. If your Initiatives + epics + stories are > 2000 then we are not able to show you the story level (either by expanding epics or with the hierarchy level drop-down)
You can check the number of issues Portfolio is trying to bring over from the "confirm what's in scope" page of the wizard. To the right of "Deselect all" there is a count of how many issues have been selected. Note that this only represents the total number of issues if you are viewing this scope from the highest level of hierarchy as it's a count of the current filter.
Okay. Thanks. The behaviour is still a bit strange considering I am taking Stories over. Does it matter if Stories are part of my Kanban Board. Will they still count against the number if they are linked to the Epics I select? If so is there a way to ensure Stories are not selected?
Portfolio is still functional if you manage your plan using epics & initiatives without stories as long as the epics in your plan are allocated estimates that represent the child stories. Unfortunately if you don't source stories then the epics cannot aggregate the estimates from child stories. You'll need to assign the total estimate of all the child stories to the epic.
The setup for this type of plan is fairly time-consuming because it requires you manually de-selecting issues in the "Confirm what's in scope" page of the plan creation wizard. This process is simply changing the view to "story" and taking the time to manually de-select every story.
Note that some minor features will be not be fully functional with this setup. For example the epic progress bar will not be impacted by completing stories as progress is relative to your plan's filter.
Thanks Rhys. This is good information to have moving forward. It is unfortunate that we don't have JIRA configured to properly take advantage of all the functionality available, but knowing what functionality we may be missing is very helpful. Appreciate the responses.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough cough, all companies). If content calendars, marketing plans, and bu...
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!
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