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

Adding reporter from Description (Smart Value)

Dear All,

I want to add the "reporter" from the description field.

Basically looks easy.

I will receive an e-mail from a certain other app (old ITSM tool) and asked that they can send me this e-mail  with <customer>"reporter.displayname"</customer>

Then when issue is created and coming from (old ITSM tool) I edit issue reporter field with


But as I learned after several tests on other subject, Jira seems to want thee JiraID instead of display name. (I tested anyway and seems right again).

Is there a way I can do that, combining smartvalues to search and match Displaynames and return JiraID ? etc...


Thanks a lot for your help!!




2 answers

1 accepted

2 votes
Answer accepted
Alex Koxaras Community Leader Aug 26, 2022

Hi @Johan Hofer 

Yes, there is a way. Kindly see the next screenshot (and replace "alex koxaras" with your value from {{issue.description.substringBetween("<customer>","</customer>")}}:

lookup and return ID.png

But here's the catch: When you lookup the issues using only the reporter's name, you have to add another field as well, to narrow down your results. In the example above, my lookupissue component yielded 139 results. So the rule only for logging the output was 7 seconds!!

Thanks a lot for your great answer. it worked.

Had other issues as displayname was not like Jira wants, but created a comment to transform text and delete it at the end of the process. Like this no need to create a custom field... but of course resource consuming.

I will check and see how it evolve with more and more data.


Thanks again @Alex Koxaras for the help

Like Alex Koxaras likes this
Alex Koxaras Community Leader Aug 26, 2022

@Johan Hofer I'm glad that it worked out!

Yeah, you should definitely watch out about this rule and from time to time try to narrow down the results of that lookup. The less, the better and the quicker the automation will be performed!

Aaaand I wouldn't suggest using this rule for multiple project or even as a global rule. :/

Just a small reply that I made the same but with lookupobject as I can find information in insight to get back to my issue

Still need to survey performance but look ok for the moment as it's during creation of an issue

Thank you again for the help and hope it can help others

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events