How to add the missing Sub-task burndown chart to JIRA Software
I am using Atlassian JIRA Software in most of my projects. But I am always using hand drawn burndown charts like this one:
But why? There are several options for burndown charts available within JIRA Software! Yes that’s true, but:
Personally I don’t like booking times on tickets. For me it is a waste of time if developers have to think about if it were 2hours or 2,5hours! So a time based burndown is not helping me.
Next there is this Story Point burndown chart. Also a great idea but in real-life, where most of the stories are closed at the end of a Sprint, that also won’t help me much.
Ok fine. Then lets go with this issue count option. Also a great idea but there is one constraint: it is only counting parent issues – not the Sub-task. Me and my team are heavily using Sub-tasks and they should definitely be included in my burndown.
How to get a Sub-task based burndown chart?
Keep in mind: it is working for us, but before using it in production you should definitely invest some time to test and make it stably running in your own environment!
You need to have the Script Runner Plugin installed within your JIRA Software instance. That plugin is charged after a 30 days trial!
Create a custom number field available for all projects where you want to use this kind of Sub-task burndown. I named it “Open Issues Counter”.
Set your JIRA Software Board to use that custom field for estimation.
Add the following content to a file OpenIssuesCounter.groovy and put it into your JIRA_HOME/scripts directory Edit 29.11.2019: Updated source code to fix breaking changes in Jira 8.0. (Stefan)
The script will be executed every 5 minutes and modify the value of the custom field “Open Issues Counter” for every issue within the current sprints of your given projects. If it is a Sub-task it will get a 0. If it is a parent task that has no Sub-tasks it will get a 1. If it is a parent task that has Sub-Tasks it will get a number telling how many open Sub-tasks it has plus the parent task itself.
Based on these values you will have a burndown based on the issue count including your Sub-tasks.
Let me know if that helped you, if there are better ways or if it is not working as expected.
Edit 18.08.2017:Big thanks to our NovaTec software craftsman community (especially Daniel Bednorz) for refactoring the source code!