I need a automation rule to copy the email address from a custom field into the Reporter field

[Hines Trulock]

Recently we starting using Jira Service Management and imported all of out customers from a database into the cloud so they are visible in the Reporter field.  

Prior to using JSM, the reporter was being tracked in a custom field called issue reporter and we capture their email address.  

Now I need to move about 3,000 issues from Jira Project to Jira Service Management and have an automation rule update the Reporter from the Issue Reporter field.  

I created the rule to be triggered during the move but it's not working to update the Reporter field. 

I tried the Field to copy value from but the custom field is not the dropdown as an option.

I've attached what the rule looks like.  Any assistance would greatly be appreciated.  

[Juan Carlos Vera]

Hi @Hines Trulock ,

Te "Reporter" in cloud, is not only an email... it have more properties like 

"accountId",  "displayName".... then you can´t inform these field only with the email.

a sample here:

"reporter":

{"accountId":"5ac37e954906585d40c0ddbba32",

"emailAddress":"jcarlos.vera@sample.com",

"displayName":"JUAN CARLOS VERA",

"accountType":"atlassian"},

For your matter... I think that you can:

• Option 1 - Copy ths Field from the same type of field in an automatrion.
• Option 2 - UpLoad all tickets with an excel, and map the Reporter in this excel with they ID in Cloud from every user,

Hope it help you ;)

[Kristopher Perez]

This is the right answer. For a little more clarity, the only acceptable value for the reporter or assignee is an accountId, whether it is from an automation or a bulk import.

Your best bet is to get a site export of all the users, and do some spreadsheet lookups to find the accountId for each email address.

if it is all in one project, you will only need the Summary, Issue Type, Key and ReporterId for a successful bulk update from the External System Import.

[Hines Trulock]

Well I seem to have actually figured it out on my own by adding the value to the audit log and then editing the reporter field.  Didn't know how that function worked until yesterday afternoon.  

Now all the issues I moved from Jira Software to Jira Service Management have the Reporter field updated by using the existing email address.  

I had already used an API to upload and create the portal customers ahead of time.  

Thanks @Sandra Axelsdottir and @John Funk for responding to help.  

[John Funk]

Hi Hines,

What is not working with the rule above? Do you get an error? Or does it just run and nothing gets copied? 

Also, it might just be how you copied it, but it appears you are missing and ending } in your JSON. And you don't need the JSON and the copy from field - you can remove that and just try with the JSON.

This also assumes that the user already exists in Jira with that email address. If not, you will need to invite the user first. 

[Sandra Axelsdottir]

Hi 

I'm curious to understand your use case. What exactly are you trying to solve and why? (if you don't mind sharing)