Release Burndown report shows incorrect data for sprints

[Karin_F]

Hi,

I have two cases for which I cannot find an explanation:

• Issue A was initially assigned to Sprint X then moved to Sprint Y when X was closed
  Sprint Y's duration was between 16 -29 JAN and the issue was closed on 17 JAN
  In the Release Burndown report this issue is represented as part of Sprint Z - duration of Sprint Z 16 JAN - 12 FEB

• Issue B was never assigned to a Sprint and it was closed on 14 JAN however it is displayed in the Release Burndown report as part of Sprint X

What I understood so far (don't know if correct) is that the report aims at showing during which sprint an issue was completed. I don't understand then why put issue A on sprint Z instead of sprint Y

And for Issue B, if it was never part of a sprint, is it randomly shown as completed under sprint X (because there were other sprints active in the same time interval)?

I would appreciate your help. 

Later edit:

after going through an already answered question on this report I found that it doesn't matter on which sprint an issue is assigned to

it only matters when it was closed which means that if you have more than one sprint active when the issue is closed it is randomly assigned to one of them 

is this really random or somehow in alphabetical order considering the name of the sprint?

Is my understanding correct?