I observed strange behavior for changes within a sprint reflected in Burndown. These are the cases:
- Issue had no completed sprint value from a former sprint and was then removed from the sprint: Issue is shown as burndown with the comment "removed from sprint"
- Issue had a completed sprint value from a former sprint and was then removed from the sprint: Issue is not shown as burndown but baseline was changed
- Issue had no completed sprint value from a former sprint and was then moved to a future sprint: Issue is shown as burndown with the comment "removed from sprint"
- Issue had a completed sprint value from a former sprint and was then moved to a future sprint: Issue is not shown as burndown but baseline was changed
As far as I see:
- a ticket is shown as burndown when there is no completed sprint in the sprint value of a ticket.
- a ticket changes the baseline when there was a completed sprint in the sprint value of a ticket.
Am I right? I don't like this behavior but now I know it.
Best
