JIRA Workflow - How to show retesting of bugs?

[s]

We are a an independant software testing company and we often use JIRA to submit bugs for developers to fix. Once they've fixed the bug they then set it to resolved / fixed, but then we need to verify that the bug is fixed. How can we do this inside the JIRA workflow? We know about sub-tasks but that means adding a new sub-task called retest for every issue (could be 200). We don't want to reopen the bug as such.

We just need to be able to create something which describes the retest we're doing. So it would contain a description, be assigned to a particular tester etc.

Can we create bulk sub-tasks or use some other feature to do this?

[Radu Dumitriu · Accepted solution]

You should extend the Jira workflow to include your states (pending test, testing, etc). I do not think it's a good idea to use subtasks for this kind of job.

[Norman Abramovitz]

I also think a state would be better because of reporting issues. It would be easier to create a workflow to make a distinction between restesting before the verification approved and restesting after verification approved.

You can use the changed keyword to find all issues changed into retest states.

You will need use a plugin or just use sql to get the count of how many times each state was entered though.

[Pedro]

I would use Script Runner plugin: https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner

Here you will find to create sub tasks, by using jython script (you can write similar in groovy) https://answers.atlassian.com/questions/25049/jira-creating-sub-tasks-automatically-based-on-a-template

[Matt]

Jira has WAS keywoard in JQL.

Have you tried to compose such JQL query like:

project = xxx AND status WAS "In Test" AND status != "In Test"

or something similar, depending what tickets you may want to catch ;}