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?
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.
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
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG