Working on issue after a sprint is finished

[Fabian]

Hi community,

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.

Thank you

[Mark de Bont]

It is advised to create a new story for a new task, specially since it is a new activity of another team (who will need to perform the estimation etc.).

Not sure what is meant by "sprint done" status. I am assume completion status

[Fabian]

Thank you very much for your advise and yes it's a completion status.