Advanced Burndown does not update on resolved issues

[Florian GOLESTIN]

While using a custom JQL, the burdown show all ticket in progress and does not reduce when a ticket is resolved

The list is correct and shows 5 tickets with 2 resolved

The burndown still shows 5 open issues while two have been resolved.

[Nic Brough -Adaptavist-]

Are the "done" issues in the last column on the board?

[Florian GOLESTIN]

Hi Nic, yes they are.

Actually the burndown get updated this morning. The tickets where resolved on 2022-02-14 and the burndown get corrected the day after (2022-02-15). Is it something expected? Is there an option for a "fresh" burndown?

[Nic Brough -Adaptavist-]

This looks like a problem with the app you're using.  I'd want to compare this burndown with the standard burndown built in, just to see if there are differences.  If the Jira one looks the same, then we need to dig into your data more, if the Jira one is accurately representing the actual burn, then it's time to look at the app.

[Florian GOLESTIN]

Sorry for the late answer but I don't reproduce the issue anymore. So I guess something was wrong in my data. Thanks for your help.