nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I use {{#lookupissues}} in the "to" of an email

Tim Foster

I am trying to send an automated email to the reporters of issues when we release into production. I have the email aspect working nicely when it sends to my email address. I am able to list the epics included in the release by defining a lookup JQL statement.

The body works fine to display the URLs for the epics included in the release. Since my JQL is defined before my email component, and my email component can access the epics without a problem, I can't understand where I'm going wrong with referencing the same smartvalue in the "to" for my email.

My "to" looks like {{#lookupIssues}}{{Reporter}};{{/}} but I get the error:

Could not send email, the 'To' address field is empty. If you have referenced a field it may be empty.

The Reporter field isn't empty, (it's me in this test), so could someone point me in the right direction please?

Accepted answers

Tim Perrault

Hi @Tim Foster

Firstly that's a cool name you got

Try using this smart value {{reporter.emailAddress}}

Thanks,

Tim

Mark Segall

Hi @Tim Foster and welcome to the community. Reporter by itself will bring up the user ID. You want to use this instead:

{{reporter.emailAddress}}

Mykenna Cepek

To help troubleshoot rules, I always like to use the "Audit log" action - in this case to see what your lookupissues smart value expression evaluates to.

In my test, it looks like this:

Screen Shot 2022-01-28 at 11.32.45 AM.png

I'm guessing that's not quite what you expected (it's not an email address). It's actually the user ID, which is what Atlassian uses to identify users.

As noted here, you probably want to write something like reporter.emailAddress instead.

Additionally, you might find problems with the trailing ; character. Remove that in your early testing when there is just one email, to confirm that everything else works in that simple case.

Then you may have to experiment with what works (comma instead of semicolon perhaps?) to support multiple emails. Reference this documentation if you find a need to use separator characters between email addresses but omit the last one.

All comments

Tim Perrault

Hi @Tim Foster

Firstly that's a cool name you got

Try using this smart value {{reporter.emailAddress}}

Thanks,

Tim

Mark Segall

Hi @Tim Foster and welcome to the community. Reporter by itself will bring up the user ID. You want to use this instead:

{{reporter.emailAddress}}

Mykenna Cepek

To help troubleshoot rules, I always like to use the "Audit log" action - in this case to see what your lookupissues smart value expression evaluates to.

In my test, it looks like this:

Screen Shot 2022-01-28 at 11.32.45 AM.png

I'm guessing that's not quite what you expected (it's not an email address). It's actually the user ID, which is what Atlassian uses to identify users.

As noted here, you probably want to write something like reporter.emailAddress instead.

Additionally, you might find problems with the trailing ; character. Remove that in your early testing when there is just one email, to confirm that everything else works in that simple case.

Bill Sheboy

Hi @Tim Foster -- Welcome to the Atlassian Community!

Yes, and...to the other responses: You may be getting an issue from any trailing delimiters, so you can selectively add the delimiter like this:

{{#lookupIssues}}{{reporter.emailAddress}}{{^last}};{{/}}{{/}}

This will add a semicolon between all the addresses, and leave off the last one.

Kind regards,
Bill

Tim Foster

Thank you, all of you, for your help. However, I am still not able to get this working correctly.

I have added a Log Action: {{#LookupIssues}}{{reporter.emailAddress}}{{/}} but it displays nothing. I have tried changing this to: {{#LookupIssues}}{{key}}{{/}} but still it displays nothing. The action details shows:

Log action

Log

But with nothing else. In the Associated Items box I can see that LookupIssues finds the correct Jira, and following this url takes me to the correct place. I can see that I am the reporter (and assignee) so all good there. Just no email.

My "To" for the email is identical to the one given by Bill above;

{{#lookupIssues}}{{reporter.emailAddress}}{{^last}};{{/}}{{/}}

But still no email.

I'm tearing my hair out with this

Tim Perrault

@Tim Foster

Try this smart value and let me know if this works {{issue.reporter.emailAddress}}

I was able to send an email, but my automation is very simple.

Thanks,

Tim

Tim Foster

Nope, still the same problem. I think I'm going to abandon the idea of the email and just have it post to the Teams/Slack channels instead.

Thanks for your help with this though. I've learned more from these boards, than anywhere else.

Tim Perrault

Bummer. Are you able to post a screen shot of the steps of your automation? I want to fiddle around with this more on my off time.

Mykenna Cepek

Hmm, actual screenshots of your rule and the components of interest might help. At this point, all I can say is "works on my box" (works in my cloud?). See below.

Screen Shot 2022-01-31 at 10.25.59 AM.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation