Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Assign Issue via Email (Custom Field) – Web Request Not Returning Expected Result

Christian Piermayr
Contributor
March 20, 2026

Hello everyone,

I’m currently stuck while trying to build an automation rule in Jira using Rovo and would really appreciate your help.

Goal:
Automatically assign a work item to a user based on an email address stored in a custom field (customfield_10145).


What I tried (based on Rovo guidance):

  1. Create variable for email:
    {{issue.customfield_10145.trim}}

  2. Send web request:
    URL:
    https://intersportaustria.atlassian.net/rest/api/3/user/search?query={{emailAddress.urlEncode}}
    Method: GET

Headers:
Accept: application/json
Authorization: Basic (base64 email)

Option enabled: Delay execution until response is received

  1. Create variable for accountId:
    {{webhookResponse.body.[0].accountId}}

  2. Edit issue → Assignee using the accountId


Troubleshooting steps:

To debug, I added comments in the rule:

After email variable:
Debug email: {{issue.customfield_10145.trim}}

After web request:
Debug: webhookResponse status = {{webhookResponse.status}}
Debug: webhookResponse body = {{webhookResponse.body}}

 

Any guidance or working examples would be highly appreciated!

Thanks a lot!

E-Mail & Web Request Comments.png

 

1 answer

2 votes
Marc -Devoteam-
Community Champion
March 20, 2026

Hi @Christian Piermayr 

When would this action take place, on creation?

Can you show your rule and details of the actions in the rule and the audit log.

But the main issue is the smart value you are using. 

Using a web request action in the rule, the smart value to use is {{webResponse.body}} 

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 Champions.
March 20, 2026

Hi @Christian Piermayr 

Yes, and...to the suggestions from @Marc -Devoteam- 

Your created variable appears to be named emailAddress, and I suggested using a variable named the same as existing smart values can cause people and rules to become confused.  Perhaps always add a prefix to variable names to avoid collisions, such as: varEmailAddress.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events