Change Reporter using Automation

[Anthony Polakos]

Overview

I'm using a Jira Cloud app (Relay Intake Forms) to create rich external forms to submit to my Service Desk. 

Issue

One of the downsides of that app seems to be no field mapping for reporter. So all issues created via the form are from a single app-created user. 

I obviously want my users to be able to access the issues they created, so I need to change the Reporter to who is actually submitting these forms.

Failed Resolution

I created a custom field for "user email".  I'd like to create an automation that upon issue creation, changes the reporter to the contents of the custom field "user email".

I'm not too hip to the exact code I should be using (or if this is even possible).

Here's what I tried under advanced:

{
 "fields": {
    "reporter": {
      "emailAddress": "{{customfield_116130}}"
    }
   }
}

How far off base am I?  🙂

Here's my automation, I have a precondition that first adds the customfield for the username and email address as a customer to Jira Service Desk (this part works!). 

Then it checks if  the reporter is the "system defined user" from the other app I use for user forms.  If it is, then change the user to the customfield for emailaddress.

I've tried various ways of inserting the reporter (email address, name, key) and none have worked.  It currently is successful on editing the issue field and changing the reporter, but the reporter now shows as "Anonymous" in the issue..

[Tom Davies · Accepted solution]

Be prepared to use an instance with plenty of memory, and you will probably want to use elastic instances for your bamboo agents.

Here are some instructions for installing most of these applications -- not including Stash: https://confluence.atlassian.com/display/ATLAS/Here+Be+Dragons

I'm not quite sure why you mention bitbucket above? -- Stash will provide your git hosting.

[Srini Srini]

Thanks Tom - this is what I was looking for.

-Srini

[Ralph Tice]

I had to compile git from source to get a new enough version for Stash, and I've had to swap out the default OpenJDK on Amazon's EC2 instances for Oracle's JDK for Atlassian products to function.

[Harry Chan]

Hi, is there a reason why you'd like to run Windows and not Linux? Windows requires more resources and isn't desired on something like EC2. We've been using EC2 and the performance can vary depending on how it's tuned. You'll have to be aware of the limited resources and tune the JVM accordingly.

If you need to run everything on one server, I'd suggest running it on a medium instance or above. Be sure to use EBS and not instance storage so you can snapshot and back it up easily. EBS optimized instances might give you more performance if you don't mind the extra cost. If you need more redundancy, I'd suggest going with RDS for the databases.

Due to the low CPU available in the small instances, you might have to do lots of tuning and configuration to get it to run smoothly.

Let us know if you need any specific help or anything else.

[David at David Simpson Apps]

You may also consider Contegix hosting e.g.
http://www.contegix.com/landing/atlassianehsp/

[Srini Srini]

David, we have decided on using EC2 and thanks for letting me know about Contegix hosting