Defect not moved to current sprint

[Andrews]

We have next planned sprint created, and then we move defects from current sprint (to be closed) to new sprint.

What exactly happening is, 2-3 defects are not getting moved to new sprint even after having in progress state and not going back to backlog items as well. Those 2-3 defects will stick back to closed sprint and remain in progress.

We want to understand what exactly we are missing or any pre-defined criteria which we are missing and hence this is happening.

[Ste Wright]

Hi @Andrews 

To be clear:

• You have an active sprint and a future sprint created on your backlog
• You are closing the active sprint and choosing to move the incomplete issues to the future sprint
• Once complete, 2-3 defects do not appear in either the future sprint or the backlog

^ If this is accurate, a simple first check is to see if there is any abnormal status / column behaviour:

1. Go to Reports on the left-hand sidebar
2. Select the Sprint Report
3. For the previous, closed sprint - check which issues show as "Completed Issues" - if the defects are in here, it might suggest that these reached a status in the last column of the board. It is the column layout, not the status, which controls sprint completion.
4. If the issues are under "Issues Removed from Sprint" - they might have entered a status which is not on the board itself. In this instance they would disappear from the backlog view as the status isn't mapped to the board.

^ If your issues are in either list under 3/4, next:

1. Go to Board in top-right - and select Configure from the drop-down menu
2. Select Columns from the left-hand menu
3. Check the status the issues are in is not in the right-hand most active column. This is the column which would be classed as "issue complete" from a sprint perspective.
4. Check also the status is not on the far-right under unmapped statuses, which would remove the issue from the board entirely
5. Fix any issues related to 3/4 (you'll need to be a Board Admin)

If neither of these are the issue, let us know so we can advise further :)

Ste