Portfolio not summing sub task estimates into user story estimate and syncing back to JIRA

[Jeff Czaplewski]

Hello, 

 I'm trying to get story points for a user story from portfolio to JIRA. currently we're estimating subtasks under the skills column for capacity planning and we have each subtask assigned to someone with that skill. so we've estimated the sub tasks  in portfolio and when you look in portfolio, the US has a light gray number in the story point field. but it's currently not getting synced back to JIRA whenever we commit changes. the only way it's getting committed back is if i manually enter the story point value on the US level which messes with our planning and isn't the way we want to do things. any thoughts?

[Earl McCutcheon]

HI Jeff,

As you discovered, Portfolio is going to take the value of the field when is manually set at the story level and pass that info back to jira, but the story point fields will show the estimated roll up value from the child subtasks.  Portfolio interfacing with and is adhering to the methodologies set in Jira.

This is by design, and Jira does not roll up values from the child issue to the parent, and is expecting story point estimation to take place at the story level, there is a really good discussion on this in the following thread, noting the accepted answer is a bit over the top, but still gets the point across and the follow up talking points cover it really well for how jira handles story point estimation:

• https://community.atlassian.com/t5/Jira-Software-questions/Do-SubTask-Story-Points-roll-up-to-the-Issue/qaq-p/339076

I also answered a similar post to this relating to how Jira is handling subtask estimation with some more details on this which can be seen here:

• https://community.atlassian.com/t5/Jira-questions/Summarizing-story-points-from-sub-tasks-in-parent-task/qaq-p/1031210

And I would also recomend reviewing these articles:

• The secrets behind story points and agile estimation
• Estimate in story points

And then this article under the expandable section towards the bottom of the article "Why not estimate on subtasks and roll that up for Velocity and Commitment?"

Regards,
Earl