EPIC burndown chart - Identifying what exactly is the scope change

[senthil kumar]

Dear all,
Either in Release burndown or EPIC burndown how to identify what exactly is the scope change.
In EPIC burndown, for example, it says "X" story points got added. How do I know what exactly those user stories?
I understood it could be either of the following cases:

• An issue is added to an epic (after it was started) with an existing estimate
• An issue that was added to an epic (after was it started) is estimated (estimate is added)
• An issue that was added to an epic (after was it started) is re-estimated (estimate changes). Note, if the issue is re-estimated in a later sprint, the scope is retroactively adjusted in the sprint that the issue was originally added to.

But is it possible to identify exactly what was changed? Even via issue filters.

Appreciate your help.

Regards
SK

[Mohamed Riza]

Hi @senthil kumar,

 Issues in the sprint are given estimates. Then they are started. If anything is done to change the estimates from the start of the sprint will be considered a scope change. This could be adding an issue to the sprint that has an estimate, or adding estimate to an issue without an estimate or changing the estimate of the issue. 

Both the Jira graph and the table will specify the reason. Please review the following screenshots: