Using onDemand service. In the past 2 weeks, the "Complete Sprint" functionality has changed. Before: closing a sprint with incomplete stories would automatically place these stories atop of the backlog. Now: getting the "Sprint cannot be completed as there are incomplete subtasks on the following issues" error.
Workaround we've started using: removing all active stories from the active sprint and then completing the sprint. But this is not very effecient.
Does anyone know why the change?
This is actually a new bug -
It seems that Greenhopper is not able to automatically move those sub-tasks to the backlog following the most recend update. Currently, the workaround is to manually remove them (as detailed on that bug report).
I actually filed that bug yesterday for this exact scenario. The only workaround currently is to manually remove the issues from the sprint, or close and re-report that sub-task, though I realize this will affect the reports.
The bug has been addressed in the code and we are working to get this released to OnDemand customers ASAP.
When you try to close a sprint, and you have parent issues not Done but all sub-tasks are Done, or visa-versa, you will be prompted to make the parent Done before continuing. For issues to be interpreted as 'Done' on your Scrum board their status needs to be mapped to that column, so if you're receiving errors for parents or sub-tasks that you believe are in fact Done, ensure that they are mapped correctly. Also there is a feature request to that functionality be implemented. So I believe it was just a casuality that you had the subtasks all completed or all incompleted.
Perhaps Olga is having the same problem I am, so I'm hopping in here. My incomplete stories have a status of "To Do" have tasks that are "In Progress". These status are mapped on my rapid board, but I am not able to close out the sprint. Any ideas?
I am having this problem on my OnDemand instance as well. I am trying to close a sprint that has a subtask open on a story and it provides the error shown below. Please advise how to resolve this issue?
Sprint cannot be completed as there are incomplete subtasks on the following issues:
I may have identified my issue. I had removed the 'closed' status from the Resolved column of my Agile swimlanes as I didnt want developers to close issues from the Agile Work view, but that left any closed issue as an 'unmapped status'.
The issues that caused the "Sprint cannot be completed as there are incomplete subtasks on the following issues" message all had one sub-task in a closed state and others in a Resolved state - since adding the Closed status back into the Resolved column of the swimlane, the problem has not reoccurred (of course it may be that Atlassian changed something, but I think the co-incidence is too great).
FTR, I now ensure developers cannot close issues by changing their security permissions - this hides the 'closed' box from the Agile Work view (which was what my original intent had been).
I am having this same problem- trying to end a sprint, but getting a message that I am unable to because some sub-tasks are incomplete. My expectation is that I would get a message like "X tickets are done, y will be moved to the top of the backlog."
|Build Date||Mon Mar 24 00:00:00 EDT 2014|
We are experiencing the same problem. Expected: Sprint is closed, incomplete issues are moved to next Sprint. Instead: Error message (image attached), Sprint is not closed. We are using OnDemand.
This is critical. Please advice.
Screen Shot 2014-11-25 at 12.07.50 PM.png
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
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