How to deal with testing issues in sprint

[Dieter Lauwers]

Hi,

We are creating issues for our developers and plan them in sprint.

The idea was that each developer sets issues to 'In review' after the development is done, so our tester can test the issue.

But, the actual testing will be done in the next sprint. Because the issues are not really closed our sprint report does not show the right evolution of the sprint. We don't have a correct view of issue open/in dev vs completed.

Our idea is now that we create 'test' issues for each issue and link them, so developer can close the issue, sprint report open vs completed shows correct evolution.

But, for me is this extra work. 

Does someone has a better way/flow how we can deal with testing issues?

Greetings,

Dieter 

[Petter Gonçalves]

Hello Dieter,

I hope you're having a nice day.

I understand that your reports are not displaying the correct data because you are not closing your issues once the Sprint is finished, but leaving it opened in an "In review" status so your testers can keep working on it. Have I got it right?

Unfortunately, I believe there is no better way to achieve your need than create new issues to properly separate both developers and testers progress and time spent in different Sprints.

If you keep using the same workflow, your Sprint reports will get messed up and not finish its tracking since you are currently performing a single issue lifecycle through two Sprints and with two different teams (Devs and testers).

The best I can recommend you would be to use a plugin to automatically create a new linked test issue once the original issue is done, avoiding the extra work. Here are some easy-configuring options for it:

- Automation for JIRA - 300 free executions per month

Creating an Automation rule:

- JIRA Misc Workflow Extensions (JMWE) Add-on

Adding a Post function in the transition that leads to Done:

Let me know if you still have any questions.