Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Email regex failing on automation rule

I need some help here.

Trying to set up an automation rule that gets the email from an issue collector form that gets added by the collector (done automatically).

I was originally trying to grab the email via a regex (I am fairly proficient in regex and have tested it online in multiple testers to validate it) and send the poster an email to notify them that we have received their issue and how to track it. But I can't even get the match to work properly.

I have tested getting the email many times with the log action. It fails every time.

Trigger: Issue Created
Then: Add value to the audit log
   This I have tried it with a basic and complicated regex. Currently I am trying: 
    reporter: {{issue.description.match(".*(parker).*”)}}

I get the same error:

Error rendering smart-values when executing this rule:Failed to get value for issue.description.match(".*(parker).*”): reporter: {{issue.description.match(".*(parker).*”)}}


I know I can get it to log when it is just



Here is a sample of what it is parsing:

this is a test

Reporter: John Doe


1 answer

1 accepted

Hi @Richard Freisberg 

When I pasted your smart value string into a plain text editor, I noticed that the second quotation mark is a slanted (curly) one:

reporter: {{issue.description.match(".*(parker).*)}}

Please try replacing that second quotation mark and see what happens.  Thanks!

Best regards,


Wow...  I never saw that!  

I will test that.. 

Ok Bill...  

I know we have all been there..   doing something over and over again, testing, tweaking, looking through documentation...  and the finally asking for help just to find out one little thing was wrong.

You found that for me!  

Thank you so much!!!

Like Bill Sheboy likes this

I am glad that worked! 

And, I wish the rule editor showed better error messages before publish and after execution.  Showing smart values as proportional fonts (rather than fixed) makes it very difficult to see issues too.  :^)

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

66 views 2 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you