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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Burndown chart is burning down before the very last column

Hi, everyone, 

I have two boards in the same project, the first one is a DEV board and the other is the TEST board, both with 4 columns. 

DEV Board columns


The developer only transit from TO DO to DOING  and finally to SEND TO TEST. 


TEST Board columns 


The Tester can transit cards in all Columns of his Board. 


When DEV team move a card from DOING to TEST, it is shown on TO TEST of TEST Board and when the Tester move from TESTING to FAIL it is shown on TO DO of DEV Board.


The problem is:

My Burndown chart is burning down when the Tester is moving the card from TO TEST to TESTING, and when the card is moved to FAIL, burndown chart burns up. 


I need that burndown chart only burn down when card is moved to DONE. 

I have no ideia how to fix it. 

Can anybody help-me? 


1 answer

Hi...  Which of your status types are "todo", "in progress", and "done" types?

When an issue is moved to one of the "done" column types, it could lead to the item showing as completed and so "burning up".

Hi @Bill Sheboy , I'll show you my "Column management"












Hi @Erik Silva 

Are these two Scrum teams with different sprints on the same backlog, or two Kanban teams on the same backlog, or something else?

Just to confirm, your workflow has these statuses, correct?

  • "todo" status values: Todo, Fail, Looks Good, Bug A Corrigir
  • "in progress" status values: In Progress, Send to Test, Testing
  • "done" status values: Closed, History Not Testable, Subtask Not Testable

And, several of the statuses are unmapped on each board, but showing on the other board, correct?

Best regards,


Like Erik Silva likes this

Hi, @Bill Sheboy  

that's right, every statuses you mention, are right.

I have one workflow, two boards but only one sprint. But when we transit the card from TO TEST to TESTING, the Burndown chart is "burning down". 


Best regards, 


Hi, @Erik Silva 

Thanks... I recall the burn chart works using the idea that the leftmost column is "todo stuff" and the rightmost column is "done stuff", with everything between as "in progress stuff".  When issues reach the rightmost column, burn up occurs.

Looking at your boards' status types and positions on the board, and the unmapped status values, there might be a hiccup...

Try this: for each board, change the filter to *only* include status values which should appear on the board.  That will exclude any of the unmapped status values from producing impacts on any burn charts.

For example, your Test board filter might be:

project = X AND status IN ("Send to Test", "Looks Good", Testing, Fail, Closed)

Best regards,


Like Erik Silva likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

4,467 views 5 15
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you