Configuring IssueTypes in a Burnup-Diagram

Dennis Lettner

Hello,

I would like to have an overview of the finished work as well as the total amount of work within a sprint (based on time estimated) to any given point in time, therefore the reports "burnup-diagram" seems to be suitable quite perfect.

The issue that I am facing right now is, that only the IssueTypes Epic, Story and Task are used in the calculation of the finished and total amount of work. This leads to the problem, that finished subtasks of a story are a part of "not finished" as long as the whole story isn't finished and they are only included in "finished work" if the whole story is finished. Am I right with this assumption?

Therefore I would need the option to evaluate in a more granular way, meaning that I would like to include subtasks of a story into the calculation instead of the whole story. The option of customizing a report in order to determine if a story or the subtasks of a story should be included in the calculation of finished/total amount of work would help.

Is there a possibility to do so and if not, will the customization of the granularity of a burnup-chart will be part of a future release?

Kind regards,
Dennis Lettner

Gabriele Franck

Hey @Dennis Lettner

This topic is indeed very discussed, but for now the sub-tasks estimation on Burndown/up reports are not considered. Jira automatically sums the estimates/logged time from the children to the parent but it does not include it sub-tasks themselves in the report.

There is currently an open feature request for this here:

JSWCLOUD-6007: Burndown chart doesn't take under consideration the sub-tasks estimation

I would encourage you to visit the suggestion page linked above and click the Vote and Watch links near the top right to show support for the feature. By doing this, it will ensure you're proactively informed of progress and updates going forward. we would appreciate your feedback on the feature, you can do this by leaving a comment on the ticket, this helps us prioritize and understand the use case of the feature request.

Also, there is this article in the community where a user mentioned the workaround they used that might be of interest to you.

 

Hope this helps!

Gabi