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
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot