There are issues which have been closed some time ago and now appear in the current sprint.
For example, there is an issue which as been resolved as "Won't fix" and closed on Jan 7th. It was not assigned to any sprint at that time and has not been touched since then.
However, now it appears in the current April sprint. Why? It has never been explicitly assigned to this sprint as you can see from the issue history.
Hey there, Thomas.
Have you tried re-indexing when you noticed this at first? One of the possibilities to this is that your JIRA might be in the inconsistent state which causes Closed issues to appear in the current sprint.
Also, can you check on the following:
If you still have issues and need urgent attention, kindly raise a ticket in support.atlassian.comfor further follow up.
I have a similar issue. I have some closed issues which upon some housekeeping suddenly got assigned to a future sprint that is not even active yet. How can I control this from happening? I got a response to disable editing of Closed issues, but I don't want to turn that functionality off.
Calling all Confluence Cloud Admins! We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...
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