The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I total sub-task types within a sprint?

Mis Mintowt-Czyz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 20, 2018

We have the following sub-task types on most of our user stories:

FE Dev, BE Dev, Test Script, Manual Test, Peer Review, etc...

I want to be able to total the Remaining Estimate for all 'FE Dev' tasks within the sprint. This will then highlight in planning if we are planning in too much 'FE Dev'.

Thanks

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Troy Spetz
Contributor
September 10, 2018

We use JIRA 7.10 server version.

We do Story Point (SP) estimates at story level (i.e. New Feature/Improvement, Defect, Tech Debt and Chore) -- but not at the sub-task level.

It seems to me that you are trying 'too hard' to micro-analyse+estimate the work required to complete a single issue (i.e. by having at least 5 different sub-task types whose separate SP estimates are aggregated to generate the parent story's total SP estimate). You are doing 'bottom-up' estimation -- as versus top-down.

If the parent story is estimated at 1/3/5/7 SPs and completed within the sprint, isn't this sufficient estimation? After all, the story's SP estimate is only needed to help the team decide how much work it can accept in the sprint being planned.

Why is it important to know that the 'FE DEV' sub-task took 0.325 SPs within the parent story's total 1 SP estimate?