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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Is there a smart value for auto-assigning users, other than the Atlassian ID?

I've setup a JA rule that pulls data from an API call, and responds with things like email, name and the unique Atlassian Id.

The component of "Assign the issue to" is set to 'Smart value' and will only take the Atlassian ID.  I was hoping it would take email address, like importing from a CSV can, but I'm not having any luck there.

Is there a way to format the Full Name or Email Address value so that it will accept it?

side note:  Ultimately, we're trying to auto-assign tasks by a combo of two values (Product & Department), on Create.  If anyone has a better solution besides building an API for this kind of lookup, I would be grateful to hear your solution.  It would be better if we had the simplest interface possible for line-of-business people to keep the lookup data updated, and would much prefer to keep this all within Jira/Confluence.    Having to lookup the Atlassian ID to store it is not the preference.  

2 answers

1 accepted

2 votes
Answer accepted
Mark Chaimungkalanont
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 15, 2021

Hey there,

If you use the email address as a smart value in the Assignee field in the Edit issue action, Automation will try to resolve that email to a user (it might not work if they've restricted access to their email)

Hope that helps!


Mark C

Thanks @Mark Chaimungkalanont !

So instead of using Assign issue, I could use Edit issue Assignee field.

Regarding restrictions, is the Automation for Jira user considered to have access if an account Contact (email) is set for "Only visible to people who have access to the organization"?

Best regards,


Hi @Mark Chaimungkalanont - maybe I'm doing something wrong, but it still won's assign me by email address, for instance, here's the rule & log instance - and yet this doesn't show up as Jira Automation in the log of the issue, and it doesn't assign me.... support ticket worthy?

0 votes
Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 12, 2021

Hi @Erin Quick-Laughlin 

Can you share your JA rule please? I mean "assign to a user" has a plethora of option, and I didn't quite understand why you've chosen the "smart value" option.


Thank you for responding @Alex Koxaras _Relational_ !

Screenshot 2021-09-13 082349.png 
(it's currently listening to priority changes instead of new issue creation, for testing purposes)

Here's what is in the log for the various web responses (with some scrubbing of values):

email = and name = Erin Quick-Laughlin and atlassianid = 5xxxxxxxxxxxxxxxxxxxd197

Using webResponse.body.atlassianid works.

When I change the rule to use or , it doesn't recognize those values to associate / assign a user.  I was hoping it could recognize a user by email, like the import process can.

Alex Koxaras _Relational_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Sep 13, 2021

From what I know, users are tied to an id, atlassianid. I don't know what the problem of using an id is, but I'll take your word for it. I would definitely check the following URLs:

If the response you are getting from the web request, is e.g. the author of a comment, then you can use another smart value, instead of the atlassianid.

Thanks for the smart-values-users link - hadn't see that before.  Helpful for the future!

I think what I'm learning here is that there's no way to code the email address to trigger JA to look it up and associate the Atlassian ID.  

If we were pulling this information from within Jira, this would definitely be much simpler.  Unfortunately, we need a way to store & retrieve users by a cross-index lookup of Product & Department - so far, I only see external solutions for that (thus the web request).  If anyone has other suggestions to keep this type of lookup within Jira, I'd love to hear it!

Hello! Did you manage to do anything good with this @Erin Quick-Laughlin  ? 
I am fine with UserId, but in that case I would need a way of getting all of my users userId's in advance. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events