Hi,
I have created a new rule in Automation. I want to receive an email with a list of issues. There is no problem creating the list, I can see that the issues I find has an assignee. I choose the assignee from the dropdown list in the To box in Send email action and saves it. Everything looks fine until I try to run the rule. Then I get the error "
{{#lookupIssues}} - key: {{key}}, Summery: {{summary}}, Assignee; {{assignee}} {{/lookupIssues}}
I change receiver in the To box to another, and run the rule to see if I could get the assignee displayed in the mail and I got this
Assignee; 712020:b6e099e3-8fef-42bc-835c-......
What am I doing wrong?
Hi Carina,
Did you think about creating a filter and then make a subscription on the filter?
Hi @Carina Gungner -- Welcome to the Atlassian Community!
For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!
Until we see those...
What type of project are you using: company-managed or team-managed?
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Carina Gungner - Can you use the below smart value and see if it helps
Send Email:
To
field, use {{assignee.emailAddress}}
.Issue Key: {{key}} Summary: {{summary}} Assignee: {{assignee.displayName}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It works in the email content to use the {{assignee.displayName}}, but using the {{assignee.emailAddress}} in the To field doesn't work. The error says "Could not send email, the 'To' address field is empty. If you have referenced a field it may be empty."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Carina Gungner , welcome to the Atlassian Community
From the error message one can deduce that there is no issue to get the assignee. Could you post your automation script so we can determine the cause behind this?
Thank you in advance for helping us help you,
Dick
By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carina,
Thank you for responding. Your query has only AND statements between the expressions. This means that the issues found would have to meet ALL the expressions.
so, issues in Project 10000 and with a duedate within 5 days, and have label Kontroll and have status done
There are no issues found, says your error message. I think that is indeed the case, because all those and statementts are a prerequisite in your query.
So I would like you to put in words, the Jira-items you would like to find and have in the email that should be sent. It'll give us a clue how we need to adapt your filter to finding the correct Jira-issues.
Thank you for posting the filter query,
Dick
By voting for helpful posts and marking answers to your question, you're helping people with similar questions find a solution more quickly. Sharing is caring applies to knowledge as well :)
Query:
(project in (10000)) AND (duedate <= 5d and labels = "Kontroll" and status = "Done")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
No there is only one issue in the list in this case, and it assigned to me
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Carina,
I think I'm missing something in the addressee field:
{{#lookupIssues}}{{assignee.emailaddress}}{{/}}
it's where you tell Jira to get the assignee from the array of tickets!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.