Is it possible to have the Burn Down chart triggered for tickets before they reach the last column?

[Omar Hamdan]

Currently the story points are burned off when a ticket is moved to the last Column which is called DONE. We want the story points to be burned off before the last column, let's say the one before the last. 

We're using the last column as the column which contains tickets that have been deployed and the column before the last as the column which contains tickets that are ready-to-be-released.

[Airbus Driver · Accepted solution]

I don't believe there is a way to achieve this because the story points are only burned off in a DONE status. Any other status is perceived as not DONE.

Even if you change the 2nd last column to the DONE status, your last column will cause issues with your reports because Jira considers the right-most column to be the DONE status.

[Jack Brickey]

The only ‘in Progress’ burndown is using time estimation.

[Omar Hamdan]

Thanks! It would be nice if this was supported though.

[Nic Brough -Adaptavist-]

It never will.  In scrum, you burn down only when an item is done.  Jira identifies "done" as the last column on the board.

The closest you might see is Atlassian allowing us to configure the "width" of that column (so you can say "anything in the last 3 columns is done", rather than it be locked to only the last one), but there's no progress on the feature request and not a lot of votes for it.