I have performed some tests in my personal instance and it seems the Sprint movements are being registered just fine, either when the Stories are automatically moved in Sprint closure or when it is manually moved:
Since I was not able to find any other persons reporting this error, please provide us the details below so we can better troubleshoot the problem:
- Are you able to reproduce the problem today? Or were these issues from the last 3 weeks all isolated cases?
- How have you checked the movement of the issues in the Sprint since they were not registered in the history? If you just saw it directly in the Sprint view of the board, it is possible that a change in the board filter caused the issues to start displaying in the Sprint view, although they were already added to the Sprint before but not displayed due to the board filter restriction.
Let us know if you have any questions.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events