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?
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".
Cheers to Kemal Bajramovic, our first ever AUG Leader to be Showcased. AUG Leaders are passionate experts who find time in their own busy lives to host Atlassian themed events to share ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot