Sprint report data actual, not timesensitive

[Martijn Hoekstra]

I use the Sprint Report data as input for a larger report. This data is generated after a sprint is closed and has completed, not completed and removed issues. Previously this data was in some way timestamped or saved to reflect the status of those issues at the moment of sprint close. However, this week I noticed it contains the current status when exporting to Excel, which is incorrect. Obviously part of the spill from previous sprint is now 'Done', but at the moment of closing the previous sprint it was still 'In Progress'.

This might be caused by the query the Sprint Report uses to fetch the issues, as it just does that. Anyone encountered the same and can help me with a fix for that?
I don't want to manually adjust all the data each sprint.

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

Welcome to the Atlassian Community!

The sprint report simply uses "sprint = X" for its reporting, there's no timestamp or saved data, it's just looking for "issue was in sprint X".  When things spill over into another sprint, you'll find the sprint field contains both sprints (or all of them if your team gets it so wrong that it goes into a third or further!)

There's no "fix" for this, it's not doing anything wrong.  When you ask for a report on a sprint, it shows you the list of issues within that sprint, with their current status.