Subtask estimate not rolling up to parent stroy

[Imran_Ali]

Hi,  I have few questions when i create a story i add two fields Story Points and Original Estimate time looking at the following example: 

• Story XYZ: Story Points:20 (and our calculation is, each point is 3hrs i.e 20*3=60hr)  so i added Original Estimate: 60h - now I have created two subtasks  under the same story
  • • Subtask X :  Original Estimate: 30h
    • Subtask Y: Original Estimate: 20h
    • Subtask Z: Original Estimate: 10h
  • Now if I burn hrs on subtask X: i.e Time spent: 25h it auto calculate Time remaining: 5h in subtask good, now my question is why this subtask is not burning hrs (Time remaining) within the main story which still shows 60h, i have to do this manually... is there any way to roll back subtask time to the main story
• Q2: how can add velocity in the sprint (like 50-60pt) 
• Q3: Is there any way to do resource planning? like if any team member is taking a day off in sprint how hrs calculate against sprint velocity? 

[Bill Sheboy]

Hi @Imran_Ali -- Welcome to the Atlassian community!

Different teams work in different ways...and... very few teams assign a number of effort hours to a story point.  That is an anti-pattern that there are other issues/problems happening, including assigning more precision and accuracy that is warranted for story point, relative sizing.

Story points help teams clarify complexity, effort, and confirm shared understanding of scope.  When all those things are working, story points could also be used for forecasting.

Back to your questions:

Q1: There is no built-in roll-up for the estimates between the parent and child issues. You can build this yourself using automation rules.  Please see here for how-to: https://community.atlassian.com/t5/Automation-articles/How-to-sum-up-logged-hours-using-automation-in-Jira-Cloud/ba-p/1409115

Q2: I do not understand what you are asking.

Q3: There are probably marketplace add-ons to do this, but nothing built into out-of-the-box JIRA.  Usually, teams just do a quick calculation on paper, whiteboard, or spreadsheet to forecast capacity impact of people being in/out of office, and then use that to forecast velocity.

Best regards,

Bill