Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sprint burndown treats both Done and other (custom) status as completed?

We recently replaced the default In Progress status (column) in our next gen project Board with several new columns: In Development, Test Ready, In Test and Test Complete.  We did not change the name or position of the Done column.

Our sprint burndown report now treats issues that are either Done or In Development as completed (see screen shot).

Is this a bug?


1 answer

Hi @Roger Rohrbach

This isn't something I've seen before unfortunately.

I did try to replicate it in our instance but couldn't. I would suggest raising it with to see if there are any known issues :)



There are many "corrupt burndown report" issues, mostly relating to classic, not next-gen, projects.

I work in a large organization wherein the Jira admins are on the other side of the world, so getting my bug report upstream is going to be a slog...sigh.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events