Version Report shows issues in wrong Sprint Edited

I am looking at the Version Report and it is showing a list of stories that were completed in each sprint.

Sprint 3

70

209

210

...etc...

However, issues 209 and 70 were closed during Sprint 2 not Sprint 3. The Sprint report shows the issues correctly, as does the Velocity Chart.

This issue seems to stem from when an issue is closed in the morning before a Sprint ends and a new sprint begins.

Why the inconsistency between reports?

[JIRA v7.1.6]

UPDATE: Further research showed this to be an anomaly that arises if two sprints are open simultaneously and you close a story that is still in the earlier sprint. Even though the story was NEVER moved to the new sprint, the Version Report uses the date/time stamp to assign the story to the later sprint. The other reports use the "Fixed Version" field to assign stories to Sprint.

This is still an odd discrepancy between the Version Report and other reports. 

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Apr 17, 2018 in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

816 views 2 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you