The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Complete a Sprint with Open Sub Tasks

Matthew Hillier
July 15, 2013

Here's one for the Greenhopper Guru's out there. I'm trying to close our most recent Sprint, however it is blocking due to some Sub-Tasks not being complete.

This is normally fine, they're typically supporting tasks that haven't been completed. But I'm going through the list of issues that Greenhopper indicates as causing issues and it's also complaining about Issues which haven't even started, or are In-Progress. Previously Greenhopper would have simply shifted these over to the next Sprint, but this time it's blocking the Sprint entirely.

Any clues would be great!

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Matthew Hillier
July 15, 2013

Finally found the issue after having a dig around in Support. Looks like a bug in the version of OnDemand that was released this Monday (15th July 2013)

Dave
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 15, 2013

You can also find related conversation at https://answers.atlassian.com/questions/190546/can-no-longer-carryover-incomplete-stories-getting-sprint-cannot-be-completed-as-there-are-incomplete-subtasks?page=1#190978

We're working on scheduling the fix and any updates will be in the bug report you referenced.

Thanks!

-dave