Things I have attempted to resolve the problem:
None of the above steps changed the number of "Incomplete" issues when attempting to Complete Sprint.
Thanks in Advance!
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.
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.
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