Burndown for dev done only (not tested)

[Chris L]

Hello, our Jira burndown currently looks like a cliff or right angle due to items not being tested. They all become dev done, and then I place them on the backlog and they will be tested later when we have testing resources. This means there's say 60 story points throughout the sprint and then suddenly 0 at the end as I move them, because the burndown doesn't consider them done. How best can I utilise Jira to handle this situation? Should we decrease the story points after they're dev done to create a burndown (just thought of that as I was typing this)? Can I create a custom report to show actual dev burndown? Thanks!

[Nic Brough -Adaptavist-]

It sounds like you have teams that test separately from the development teams (or at least, different processes).  In this case, they have different definitions of done, and hence should not be using the same board or sprints if you need to be doing anything resembling Scrum sprints and burndown.

Imagine a process for an issue of

To do -> development -> dev-done -> testing -> all-done

The developer's board should only have the first three steps as columns (optionally with testing and all-done in the done column), and the tester board only has the last three.

This enables you to get useful burn-down out of each team, but does have complexities in reporting overall, and can be confusing when you get your testers and developers together for some reason - you'll have developers saying "it's done" to testers for whom it is "to do" or "in progress".