Checking for Reporter Status in an automation

[#1]

A client told me that one of their automations was failing but only very sporadically. One of the steps in the automation clones the current work item and then links the cloned version to the trigger issue. The failure came when the Reporter from the trigger issue was no longer an active user in the system. This caused the automation to fail on these very occasional occurrences. 

The simple solution is to set the initiator as the reporter on the cloned work item. If you want to do this, when you Clone the work item, set the Reporter in the Clone ticket to {{initiator.accountId}}.

In the case of my client, this solution works. However, in many cases, you really do want the original Reporter to be carried over to the cloned work item. In that case, you need a few steps to manage this potential problem. Following is a step-by-step guide to addressing this problem. 

1. Get the status of the Reporter

The first step is to determine whether the Reporter is active or inactive. This Webhook call will respond the needed information.

You will need to create the Authorization information. To do that, see this page.

2. Create a variable with the original Reporter account Id

Steps 3 and 4. Check whether the user is active. If not, then use the Initiator as the reporter

Step 5: Clone the work item with the newReporter variable as the Reporter.

[Bill Sheboy]

Hi @Derek Fields _RightStar_ 

Thanks for your article.  You may want to move this one from the New-to-Jira group to the Automation product area:

https://community.atlassian.com/forums/Atlassian-Automation/ct-p/automation

Kind regards,
Bill

[Valecia Goodnow]

Good info

[__ Jimi Wikman]

Excellent article @Derek Fields _RightStar_ !