Release Burndown chart shows Story Points of issue completed outside of sprint as work remaining. 

Issue Summary

Release Burndown chart shows Story Points of issue completed outside of sprint as work remaining. 

Scenario 1: An issue was already in progress when adding to the sprint and it was later closed outside of a sprint and added back to the Sprint. Now the Story Points of this issue will continue to show in the release burndown chart as Work Remaining.

Scenario 2: Issues completed outside of the sprints, when added to the Sprint, the Story Points of this issue will continue to show in the release burndown chart as Work Remaining.

Steps to Reproduce

All issues were associated with version v1.2:

Started Sprint 20:
Created the below issues in Sprint before starting the Sprint
SCRUM-17 with Story points 1
SCRUM-18 with Story points 2
Thus original estimate before the start of version 1.2 = 3 (Light blue section of the bar)
Moved SCRUM-17 to Done status (-1)
Marked the Sprint completed and moved SCRUM-18 to future Sprint Sprint 21.
Created a new issue SCRUM-19 with Story points 3 i.e. work created after the start of the version. (Dark blue section)
The release burndown shows the data correctly.

Started Sprint 21:
issues present in Sprint before starting the Sprint:
SCRUM-18 with Story points 2
Issues added to the Sprint after the sprint was started:
SCRUM-19 with Story points 3. This issue was in "In Progress" status while the scope change.
Moved SCRUM-18 to Done status (-2)
Marked the Sprint completed and moved SCRUM-19 to future Sprint Sprint 22.
Created new issues SCRUM-20 with Story points 4 & SCRUM-21 with Story Points 5.
The release burndown shows the data correctly. The new Work added(dark blue section)after the start of the version correctly shows as +9. The bar correctly shows -2 work completed(green section) & correctly shows work remaining(Light blue section) as 3.

Started Sprint 22:
issues present in Sprint before starting the Sprint:
SCRUM-19 with Story points 3
Issues added to the Sprint after the sprint was started:
SCRUM-20 with Story points 4. This issue was in "In Progress" status while the scope changed.
Moved SCRUM-19 to Done status (-3)
Marked the Sprint completed and moved SCRUM-20 to future Sprint Sprint 23.
Created new issues SCRUM-22 with Story points 6 & SCRUM-23 with Story Points 7.
The release burndown shows the data correctly. The new Work added(dark blue section)after the start of the version correctly shows as +13(=6+7). The bar correctly shows -3 work completed(green section) & correctly shows work remaining(Light blue section) as 9.

Started Sprint 23:
issues present in Sprint before starting the Sprint:
SCRUM-20 with Story points 4
SCRUM-21 with Story points 5.
Moved SCRUM-20 out of the Sprint then moved it to Done status and moved it back to the Sprint.
Issues added to the Sprint after the sprint was started: None
Marked the Sprint completed and moved SCRUM-21 to future Sprint 24.
The release burndown shows the data correctly. The Work added(dark blue section) correctly shows up 0 since no new issues were created after the version was started. The bar correctly shows 0 work completed(green section) since SCRUM-20 was completed outside of the Sprint. But the bar incorrectly shows the total work remaining(Light blue section) as 22 since at the start of this Sprint total Story Points of SCRUM-20, SCRUM-21, SCRUM-22 & SCRUM-23 were 22(=4+5+6+7) and then we closed SCRUM-20 outside of the Sprint thus now remaining Story Points of SCRUM-21, SCRUM-22 & SCRUM-23 is 18(=5+6+7).

Started Sprint 24:
issues present in Sprint before starting the Sprint:
SCRUM-21 with Story points 5
SCRUM-22 with Story points 6.
Moved SCRUM-22 to Done status
Marked the Sprint completed and moved SCRUM-21 to future Sprint Sprint 25.
Issues added to the Sprint after the sprint was started: None
No new issues were created.
The release burndown shows the data incorrectly. The new Work added(dark blue section)after the start of the version correctly shows as 0 since no new issue was created. The bar correctly shows -6 work completed(green section) as SCRUM-22 was set to done status & Incorrectly shows work remaining(Light blue section) as 16 since the total work remaining for this version is for SCRUM-21 & SCRUM-23 and thus the correct remaining story points should be 12(=5+7).

Started Sprint 25:
Issues present in Sprint before starting the Sprint:
SCRUM-21 with Story points 5
SCRUM-23 with Story points 7.
Moved SCRUM-21 & SCRUM-23 to Done status
Marked the Sprint completed, as there were no issues remaining hence we didn't get a prompt to move issues to the next sprint.
Issues added to the Sprint after the sprint was started: None
No new issues were created.
The release burndown shows the data incorrectly. The new Work added(dark blue section)after the start of the version correctly shows as 0 since no new issue was created. The bar correctly shows -12 work completed(green section) as SCRUM-21(+5) & SCRUM-23(+7) were set to done status & Incorrectly shows work remaining(Light blue section) as 4 since the total work remaining for this version is 0 now as we do not have any other issue associated with this version!!

Expected Results

The issue that was completed outside of Sprint, it's Story Points should not show in the release burndown chart.

Actual Results

The issue that was completed outside of Sprint, it's Story Points is showing up in the release burndown chart as Work Remaining(Light Blue section of the bar of all subsequent Sprints!!)

Workaround

Currently, there is no known workaround for this behavior.