How to handle issues in testing at the end of the sprint

[Deleted user]

Hi,

At the momentwe are using jira in a Scrum setting for our development team. The problem we encounter is that when we finish the sprint and the testers did not finish the testing in time we keep the issues to test around and they move through to the next sprint. This however has the problem that in the final reports and story point calculations these points are also calculated as not being finished.

Is there a way to get the reports reflect a correct amount of points which developers can handle, so that we can plan accordingly.

[Thomas Schlegel]

Hi Sebastian,

you could remove your testing status (and the following) from the sprint. The final, mostright column on your board would be "end of development" then and if you close the sprint, the issues will not be moved to the next sprint, because for this board, they are considered done.

Your testers will need another board for their testing or do the testing without a board.

[Deleted user]

This is what I did in the first place, but the problem was for now that We added the testing issues later again to the sprint, which then draws some kind of crooked picture of the sprint since the points will appear in the next sprint.

Now while writing I realize that I either could set the points to 0 for the testing issues before starting the new sprint, or create a Kanban board for the testers and a Scrum board for the developers.

I'll try this, thanks

[Thomas Schlegel]

You're welcome, @[deleted]