Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Burndown chart on Subtask level

Every now and then, the question pops up, why does atlassian invites to use subtasks, but they dont show in the Burndown chart.

The answer is: no, that does not work. Some people help themselves with add ons and twisting and configuring them, that it somehow works out.
But until now, Atlassian did not provide a simple solution to that simple demand.

However, my personal solution is, that I reorganize my projects and boards in a way, that a story/task is the lowest level in my boards. As they are shown in all charts when closed, they need to be refined as much as possible, to have a chance to be set to done in one single sprint.



Hi @Dilip Abegune

Disclaimer: marketplace partner

Interesting workaround! We noticed the same challenges with subtasks and handle them cleanly in minware!


In addition to accounting for subtasks in our burnup charts, you can dive into the subtask layer on our predictive roadmaps and value stream reports.

nice & thanx! I will check this out.

@Dilip Abegune Great, let me know how we can help!

It is important to understand what Atlassian is doing with Jira Software.  It supports Scrum and Kanban, of course. 

But the implementation of sub-tasks is a bit of a hangover from the original "scrum" process (and totally accurate for Kanban) whilst trying to not to annoy people doing Waterfall.

Sub-tasks are not sprint items, they are a fragment of a sprint item. So you should not "burn down" on them.  Burn down is for sprint items.


Log in or Sign up to comment