You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are currently experiencing this problem where closed issues are showing up on a sprint when the issues were not on the backlog so the user couldn’t have moved it to the sprint. The user started the sprint without these tasks in the sprint container.
They appeared as closed once the sprint started.
We investigated and some of the issues had a change in the sprint value prior to the start of the sprint - there was a change 6 days ago where the the sprint value now included the new sprint name however the user indicated the tasks are not on the backlog so couldn’t have moved it into the sprint.
Is there any way these issues would be added to the sprint then?
We have checked the column configuration of the board and all "green" status are in the correct far right column.
Hi @Drishti Maharaj , being in the backlog isn't a requirement to be able to move an issue to a sprint. If the active sprint is somehow being added to the Sprint field then it will be added. BTW "closed" issues will not generally show in the backlog. Some questions:
As I stated above being in the backlog isn't a requirement to appear on backlog and closed issues would not be on backlog. The question is - who or what is updating the Sprint field on closed issues? This should not be happening and should be corrected.