How does Sprint Report identify stories added to sprint after start?

[jodywhite]

There's not a way to return this in JQL, and I read that it's not returned via an API call either. So how does the sprint report know which stories to flag?

[Bill Sheboy · Accepted solution]

Hi @jodywhite 

Short answer: from the issue history.

The changes to issues are recorded by the date / time they happen.  When the issue is added to a Sprint, the specific changes and when they happened are added to the history.  The Sprint report reviews the issues which are (or were) in the Sprint and parses the history to identify what was in scope at start, added later, removed, re-sized, etc.

Kind regards,
Bill

[Petru Simion _Simitech Ltd__]

@jodywhite  

While you can analyse each and every issue history to see if the issue was indeed added to the sprint (the updated value in the history is the Sprint field) and that happened after the sprint was started, this can be time consumming and can not be easily exported for further reporting and analysis.

If you are open to apps, you can use Issue History Dashboard for Jira, an app released by our company. 

https://marketplace.atlassian.com/apps/1235591/issue-history-dashboard-for-jira?hosting=cloud&tab=overview

A search for Field Updated - Sprint and the Date of Change from and to  reflecting your sprint start end dates will provide you will all issues that were moved in and out of the sprint. Considering that issues can be repeteadly moved in and out and the number of such issues can be large you might benefit from a quick overall report of all such issues. The result can be exported to CSV for further analysis and reporting.

Regards, 

Petru