Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Burnup chart not reflecting the changes correctly

Vikas
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 16, 2023

In Dashboard, we have multiple columns with status associated in the bracket as listed below. The issue is when we move the task to Code Review column, the Burnup chart should move up considering the task has reached the status as done. However, the chart reflecting only when we move the task to Done column which is the last column in the dashboard. 

We would like to move the chart once the task reached the first done status which is Code Review column in the board. But its not working. Any help in this matter would be greatly appreciated. Please note, we have multiple columns with Done status. 

Columns
ToDo (ToDo)
Pre-Dev Review (ToDo)
In-Progress (In progress)
Pre-code Review (In progress)
Ready For Testing (In progress)
In Testing (In progress)
Code Review (Done)
Staging (Done)
Verified in Stage (Done)
Production (Done)
Done (Done and Close)

1 answer

1 vote
Walter Buggenhout
Community Champion
January 16, 2023

Hi @Vikas and welcome to the Community!

Your analysis is 100% accurate: an issue is considered to be Done on a board when it reaches the rightmost column of the board. Regardless of your workflow, that's the way it works and there is nothing you can do to change the behaviour.

Two potential workarounds may help you get around this:

  • you can map multiple statuses to the rightmost column of your board, which makes the board consider all these statuses as done (and so reflect that in the burnup chart). An obvious downside is that you cannot drag issues into the next status anymore and you'll need to update issue status from the issue detail view instead.
  • If you consider the status change to Code Review as a handover to another team / discipline, you could set up a second board that uses this Code Review as the first status and the following statuses as other columns. So basically: split your process across two different boards.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events