Sprint Completion -- All items in sprint are done, but says items incomplete

[David Patrick]

Steps:

• Conduct normal sprint activities, creating, completing, adding, logging time against, issues
• When at end of sprint and all issues are "Done", attempt to "Complete Sprint" from Sprint Board
• Warning pops up stating that there are 19 incomplete issues that will be moved to the backlog (there are no incomplete issues (there does not appear to be any way to determine what it considers "incomplete")

Notes:

• All issues are in a "Done" status (tasks, subtasks, bugs, etc... everything is in a final status, we have double and triple checked)
• When searching the issues in the sprint to try to determine which are the 19.... (maybe related to problem, not sure)
  • 19 issues were reported by a single user (all of type Task or Sub-Task)
    • user reports that they created many of these issues after the Sprint started (either as sub-tasks, or by creating in the backlog and moving into active sprint)
  • 19 issues are in the Type = Bug OR Task

Things I have attempted to resolve the problem:

• ensuring all issues in the sprint are in a "Done" status
• switching the workflow used by Task types in the current project to one that I know works in other projects
• set remaining time estimates on all issues in Sprint to 0m
• ensured that all tasks were in a Resolved state for their Resolution

None of the above steps changed the number of "Incomplete" issues when attempting to Complete Sprint.

Thanks in Advance!

David

[Ryan Ovens]

Hi - We have this same issue and it appears to be the rightmost column that Jira sees as Done, however, we also have a Cancelled status which is also Done (and only one column can be the rightmost!). So when completing a Sprint, we obviously don't want to move the Cancelled issues anywhere. It seems wrong that Jira bases it on the column location rather than the fact that both statuses are members of the Done category. Is there a workaround here or do we just have to accept that we need to delete the tasks or move them to Done status? We are on a team-managed project. TIA.

[Nic Brough -Adaptavist-]

It's not "wrong", the last column is how Scrum and Kanban define it.

For company-managed (classic) software projects on Cloud (And all Software projects on Server), the boards can work fine with you on this - you map the "cancelled" status into the "done" column.

For team-managed projects, and business projects, no, there's no "fix" for this (yet).  The best you can do is what Atlassian expect you to do - mark the issues as "Done" by putting them into the column, but use a resolution such as "cancelled" to say why your team thinks they are done.  It makes reporting more painful because you will have reports that now need to select for "done and resolution != cancelled", but you don't lose data this way.

[Ryan Ovens]

Can you advise how to define the Resolution field in the Team-Managed version as you have suggested please? We can't seem to find it. Thanks.

[Nic Brough -Adaptavist-]

Resolution is a system field, but one that is (effectively) handled automatically by team-managed projects.  You don't add it and you don't need it in those projects.

[Ryan Ovens]

Thanks. So your previous comment is incorrect then. We have removed the Cancelled status and simply made a custom field for the resolution.

[Nic Brough -Adaptavist-]

There's a couple of things this could be, but let's start with the easy one: are all the issues on your board in the far right hand column?