Removing issues from sprint - any logic?

Hello,

we are using Greenhopper and have a board with an active sprint, several sprint markers and backlog. When I remove issues from active sprint sometime they are put to the backlog and sometimes to the next following sprint marker. Is there any logic what Greenhopper is doing in this way?

Thank you!

1 answer

1 accepted

Accepted Answer
0 votes

The theory is below (stolen from https://confluence.atlassian.com/display/GH/Ending+a+Sprint ) but I've heard of cases where it's not doing exactly that. Seen it a few times myself, but always been able to track it down to a dubious definition of "done" in our more peculiar projects. I am not entirely sure how it decides what the "next planned sprint" is either (I'd suggest it should be by date, but I don't actually know)

Any issues not completed at the end of the sprint will be returned to the backlog (or to the next planned sprint, if you have one) as they did not meet the team's definition of "Done".

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Agile

What's new this quarter in Confluence Server - August 2018

Hello Atlassian Community! My name is Ada , and I'm the Product Marketing Manager for Confluence Server at Atlassian. If you missed   our last post, we're transitioning to quarterly updates&nb...

155 views 0 1
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you