Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Trying to set the 'Company' field by pulling from the Reporter's Email Address for Emailed Requests

Evan Gilner
Contributor
September 13, 2021

So our Service Desk actually supports multiple intertwined "companies" (though we work very closely together under the same roof and all use the same JSD instance and project).

Users often choose to email their requests to the Service Desk rather than submitting them through the Portal. In this case, the tickets often come in with the Reporter being the user's full email address, rather than the user's actual Jira account. 

Currently we default all Emailed Requests to one company, even though users from each of our companies will email the Service Desk to create a ticket.

 

I've been attempting to build an automation that pulls from the user's email address to set the correct company for Emailed Requests, but Legacy Automation throws the error: "The operator '~' is not supported by the 'reporter' field." And the newer Jira Automation doesn't support field modification at all currently. 

Screenshot 2021-09-13 124614.png

 

I've tried the "reporter.property" field that comes up but get the same error. Not sure why the 'contains' operator doesn't work for these fields, and also not sure how I can get around this issue without that operator.

 

Any help would be hugely appreciated!

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 13, 2021

Hi @Evan Gilner 

When you note "the newer Jira Automation doesn't support field modification at all currently", what do you mean?  Is there a specific field that you are unable to edit with Automation for Jira?

Kind regards,
Bill

Evan Gilner
Contributor
September 16, 2021

Hi @Bill Sheboy 

I'm not sure when the Atlassian Team changed this between when I last tried and now, but it seems that the field modification I am looking for has, in fact been added. I could be wrong but I swear it wasn't there before. 

So, because your response led me to check again, and thus discover the functionality exists, I have accepted your answer!

Thank you very much,

Evan

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer