Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

how do I track burn down using sub-tasks where the top level is a user story

First time using JIRA in this style, but a consulting firm organized the project in a way that User Stories are both a Confulence Page and a JIRA Story item. All the developer work and testing is occurring as tasks and sub-tasks related to the story.

Stories go from ToDo - Approved - In Progress - Complete - Accepted - Done

But Tasks (and subtasks) go ToDo - In Progress - Complete - Done

How do I get a burn down report on tasks and subtasks? Or do I have to force stories to done?

1 answer

1 accepted

2 votes
Answer accepted
Jack Community Leader Dec 19, 2017

You simply need to do your estimation, time logging and remaining estimate updates on the sub-tasks. Have the stories sum up from sub-tasks. Stories should be defined such that they can be completed w/in a single sprint ideally. Stories and Tasks should be placed into a sprint which will result in your burn-down being calculated correctly.

A couple of other thoughts based upon the info you provided:

  • Stories should remain in backlog until they are in Approved status.
  • Approved stories would be allocated to the left most column on your scrum board.
  • IMO, tasks = stories but your requirements may drive the different workflow.

What you say makes sense... but how do I have stories sum up from tasks and subtasks?

To be clear we have

Stories

---Tasks

------sub tasks

all the time is tracked at tasks and sub tasks.

 

I agree with your thoughts and yes, stories are written to be completed in one sprint.

At this moment, the burn down is not showing anything but a flat line, except when something is added to the sprint (new bug)

Jack Community Leader Dec 20, 2017

You enable sum up on the specific story itself. There is a check box in the view issue screen where time tracking is located. However, if you are not seeing any burn down this is not the source of your problem. Here are some things to check:

  • in the Board settings under the Estimation view please ensure you have Remaining Estimate and Time spent checked.
  • make sure that there is an Original Estimate for every task, ideally prior to starting the sprint.
  • make sure that time logging is actually occurring on an active sprint.

Note in your last response it seems you are indicating that Tasks are a child of Stories and sub-tasks a child of tasks. While you can link a task to a Story it isn't really a child like a sub-task is. Regardless, this fact doesn't effect the burn down, any issue in a sprint that has an OE, time spent and remaining estimate will count to the burn down as designed.

Like Shashi Annasagaram likes this

Thank you. this makes sense. The consulting team is wanting to avoid this, but it seems the best solution.

So as for tasks and stores... yes I get what you are saying. Tasks are linked 

Hi @Jack, would you be able to elaborate a little more or share a screenshot on where I can get this checkbox enabled?

You enable sum up on the specific story itself. There is a check box in the view issue screen where time tracking is located

Jack Community Leader Jan 29, 2019

the box will show up if you have estimated time for the task otherwise Time Tracking fields are not displayed.

include sub-tasks.jpg

Like Shashi Annasagaram likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

145 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you