The best way to differenciate dev tickets and prod ticket and have both count in burndown char

Karol Sykała

Hi,
from my research I've found that the sprint burndown charts etc. count only the last column, which is not ideal, since our project differenciates develop from production tickets. What is the best way to still have clear separation between tickets on production and develop and still have them both counted as done in jira raports/burndown charts?

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Burn down charts are based on "done", which is a short way to say "the team does not need to do any more work on this issue".  As that's quite a simple discriminator, Jira keeps it simple - "done" is the last column, where people can simply ignore issues in that one column.  You don't really want them having to think about multiple columns, the clearest option is "last column = done"

The simplest way to have a separation is to have a field on the issues that tells you whether an issue is production or development, and have their "done" status all mapped into the last column on the boards.