We're facing an issue where tasks or bugs marked as closed are automatically move to the next sprint when I close and open a sprint.
It seems to happen in regular tasks and in sub-tasks as well. To make things clear, the sub-tasks are closed and their resoultion is "done" along with the parent task. When I close the sprint they move along other "in progress" tasks to the next sprint.
What make us more puzzled, is that although the status ("close") was created by us, we did set the resoultion to "done".
Would really appriciate any help here.
I suspect your issues were not in the right-hand column of the board when you closed the sprint.
Issues that are not in the right-hand column are not considered "done" by the board, so they will go to the next sprint or into backlog when the sprint is coled.
It seems that you are right.
However, I'm not sure why. What really happens behind the scene when I predss the "Move to Done"?
We mainly do everything using the API using our CI so I'm not sure how to move them to the right hand of the board automatically - we change the status and resolution using the API.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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