Automated Testing Emails to Business Domain Testers with Responses Updating Issues

Bradley Rosenberg

Hello!

I wanted to see if there was a better, more automated way to handle business domain testing.

Today, whenever a feature is ready to test, a developer moves the Jira issue to the status of testing, copies the list of testers from the issue, creates a new email off of a template, and sends the message to all of the testers asking them to test and response with "Success," "Failure + {text}," or "Question + [text]".

I've tried searching for a way to automate this process to the email automatically goes out to set testers when an issue moves into the status of "Testing," and so that the responses automatically update the ticket.  The automatic update would give the assignee an alert, and ideally the issue would move to the next status if all set testers replied with "Success."  So far, the best option seems like the ScriptRunner tool, but that requires some investment.

Some amount of the testers are not,  in fact, Jira users, so that adds another wrinkle.

Is anyone doing this today?  Does anyone have any recommendations?  Thanks!

Mark Segall

Hi @Bradley Rosenberg and welcome to the community!

So if I understand correctly, you're looking for the ability to send emails to a group of designated testers and when they respond have their responses captured in the issue?  This is tricky indeed.  The added wrinkle of not all testers having Jira accounts adds complexity. 

The only way I can think of this natively is by leveraging JSM.  It would work something like this...

1. Issue Transitions to Testing
2. Automation creates a new linked JSM request and adds the list of testers as participants (assuming they're captured somewhere on the original request)
3. Automation adds a public comment to the new JSM request to inform the users that they need to perform testing.  All participants receive the email
4. Responses come in to the JSM request.  They can either stay here or another automation can copy the comments over to the original issue

Again, this is predicated on having JSM licensing