I've currently problems in completing a sprint, due to the 'famous' "Sprint cannot be completed as there are incomplete subtasks on the following issues" message.
All subtasks of the issues in our sprint have a Done-Category status (Done or Obsolete)
and all subtasks of the issues in our sprint have a resolution (Done or Won't Do)
I don't understand why this is happening.
I've for testing purposes transitioned one subtasks (after marking it with a label) from Obsolete -> Done
and it's parent Story is not showing up in the list on a close spring attempt. So it definitely has something to do with the custom status/resolution.
Any ideas? Thanks for your help in advance!
I am having a similar issue. I have two "Category - Done" statuses (Done and Rejected) and both are in the far right column. If an issue is in the Rejected Status and the sprint is completed it automatically moves them to the next sprint. Being that the issue was rejected(Done) in that sprint, why does it not stay with that sprint? Is this a user setting or default setting. Can it be changed?
I mean if you have a sub-task which is Obsolete, still the user is forced to move it to done column. For lot of teams this is highly unintuitive as when you move an issue to "DONE" column then you see two areas to drop the issues (complete or obsolete) and it's hard to convince SM/POs that even if the issue is obsolete still it should be moved to *Done* (which implies work done) in order to close the sprint (in case it's a obsolete sub-task of a done story)
I hope Atlassian implements this feature request soon - https://jira.atlassian.com/browse/JSWSERVER-12169
I had a quirky situation where Jira would report that "Sprint cannot be completed as there are incomplete subtasks …" while all the issues and their subtasks were actually closed, with proper states and resolutions set.
This was because a closed status called "Trash" was hidden, i.e. it was no assigned to any column on the board. As soon as I added it to a column, Jira stopped complaining.
My way of solving this is to mark all the subtasks that have been moved to the new sprint as done first (since it is causing the problem), then I will be able to close the previous sprint. Then only I change the status of the subtasks in the new sprint from done to its respective status.
I had the same problem, when I try to complete a sprint with one story completed with all its subtasks completed and is showed same message: "Sprint cannot be completed as there are incomplete subtasks on the following issues".
I observed that Jira only allows a sprint to be completed on a board that has configured all the "completed" states of all the items (issue type) that exist into the Sprint in its green column (Done). The problem is that the 'Done' status of the task is not configured in the green column.
For example, if we have stories with status "Accepted" (green color, Accepted & Done column), "Deployment" (green color, Accepted & Done column) and "In Production" (green color, Accepted & Done column); and tasks with status "Done", we must have a board that integrates both issues Types and a green column (green color, Accepted & Done column) with the "Accepted", "Deployment", "In Production" and "Done" states into green column.
If you integrate all the issue types and all the states in a board (or new board), then the problem is solved in that board;
and now you can to complete sprint...
So I have a bizarre scenario. I recently joined a new team and converted them onto JIRA. However I joined sort of during a sprint and by the time everything in JIRA was set up most of the work was done but the team didn't moved to JIRA until the second sprint began. Since we didn't set up the first sprint on time, and I added the issues to the sprint retroactively (for tracking) even though the time on the sprint is done and all issues and subtasks are in done status and the statuses are mapped to the correct column, JIRA still won't recognize the issues as done! It's super frustrating because I need those issues gone from the backlog view :( ... any suggestions?
Best you can do is a dummy sprint (ideally between ending the current sprint and starting the next one). It'll make the velocity look odd, but close everything off.
The other option is to have a very funny looking sprint which includes all the closed ones.
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