Hi @ilker işler
From looking at this question, it does not appears that there is any configuration change that can be made to Jira Software in order to have these subtask estimations included into the burndown chart.
There have been a number of feature requests and bug reports posted on this, and you can find the current report on this in https://jira.atlassian.com/browse/JSWSERVER-6007
From looking at some of the related cases on that I came across a different suggestion on using Jira a bit differently from one of the Agile team members that might be helpful instead, @Kiran Shekhar had this comment on https://jira.atlassian.com/browse/JSWSERVER-12536 :
Unfortunately this is only supported with time based statistics by enabling 'Time Tracking' in the estimation configuration for the board. You might like to try using Time Tracking but having 1 hour = 1 point, this will achieve what you're looking for.
Other option, is instead of using Story and Sub-tasks, you could try mapping the parent issue to an Epic issue type and the smaller tasks to Stories. This way you can also get reports to even track the progress of the Epic.
JIRA Agile Team.
Sorry if this is not exactly what you are looking for, but I hope this helps.
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs