we are looking for a good way to work with user stories after a sprint is done.
A team is working on a user story and wants to move it in a "sprint done" status.
After that an other team is picking up the story for external testing.
If I understand it correctly a user story has to be closed in order for the sprint to be closed and the reporting (e.g. burn down charts) to work.
I was thinking of creating a new story (cloning by using automation) once the old one is done and assign it to the new team or would it be enough to set the remaining story points to 0 when the issue is moved to "sprint done"?
I hope you have some ideas for me.
Hello Community! Quick disclaimer: We are running a contest on Community (The Atlympics!) from July 23rd - August 8th of 2021. If you are interested in participating in this contest (prizes! ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events