I have an Epic with >10 issues and two of those issues have a fixVersion set for a release. The plan I have is for that fixVersion and only the two issues are showing under the Epic in the plan, which is correct. The two issues come to 6 story points in total, 3 each. But the roll up figure for the Epic is showing 16, assuming its counting SP for issues not for the fixVersion.
I think I found the cause. My View Settings are set to GroupBy 'Team'. So the other issue which should have been part of that Epic (with that fixVersion) was in the plan but was in the Unassigned list (i.e. wasn't associated with a Team). When I assigned the correct team, it moved up into the Epic assigned to the team in question and the Story Points at Epic level made sense. Actually the SP were correct all the time, its just that the missing issue hadn't been assigned a team. See resolved screenshot below.
Apologies for the 'red herring'! Am just getting going with Portfolio for JIRA.
My previous query has been resolved thanks. But I have a related query;
The roll-up feature; issue's story points rolling up to Epic level. What I'm observing is that the roll-up doesn't apply the filters which I have set on my plan, is that expected behaviour? E.g.
I have a 'release' filter set to 2.0.0 in the plan and I have an Epic which has both 2.0.0 issues and 2.1.0 issues. When I expand the Epic in the plan, it shows the 2.1.0 issues, but they are greyed out (which is fine), but the rolled-up story point figure counts both 2.0.0 and 2.1.0 issues. Expected or not?
Hello again @Christopher Foley
It does indeed sound odd. I would have similar expectations to you with regard to the filter application in the roll-up feature. However, I am not fully sure how these filters work and on what level they are applied. By looking at the documentation of the roll-up feature (https://confluence.atlassian.com/jiraportfolioserver/rolling-values-up-to-parent-issues-968677334.html) it does seem as though the filters that apply to it are set in the "View Settings" and external filters don't apply.
We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...