Issue with my burndown chart not reflecting work logged?

[Ashley Freeman]

Hello! 

We had a task with an original estimate or 4 weeks. We logged 2 weeks of work during Sprint 1, and the remaining estimate was then 2 weeks. We moved this task to sprint 2, and expected to see the burndown chart to go up by 2 weeks since that the remaining estimate, but instead it went up by 4 weeks, the original estimate. Why does the burndown chart reflect original estimates instead of remaining estimates, and is there any way to change this?

This is also an issue because we can't see that work is actually getting done according to the burndown chart, because we don't see any burndown until the issue is in the "done" status, and then the burndown is seen all at once.

[Dharma Ramos]

Agree with @David Leal . Would like to add, work should be broken down into smaller chunks that can be completed within the sprint to achieve a potentially shippable increment by sprint's end. 

[David Leal]

As far as I know this is the expected behavior. Jira burns the effort (points or time) once the issue reached the right-most column of the board. Here you can find more information about Jira board specification:

https://confluence.atlassian.com/jirasoftwarecloud/burndown-chart-777002653.html