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; } } }

Sending e-mail notification to in automation just created issue fails

Martin Flury_3s1d00

Hi all,

I'm kind of stuck and can't see the error.

The automation is set up like:

- trigger every two weeks

- creat new Task Issue

- send notification to assignee

But the Audit Log shows an error at the last step sending the notification mail, as no issue is present so it can not get the assignee. BUT the issue has been created correctly

Why isn't it getting the just created issue and assignee of it?

The new Task issue is existing and I got assigned in it, but I never got any notification about it.
Somehow I should generally get a notification when a newly created issue is assigned to me I think. At least that was the case so far and we have not actively changed anything.

The solution looks like this:

Accepted answers

Jack Brickey_h10pa4

Hi @Martin Flury , try adding a re-fetch data action before sending the email? This often times fix similar issues where there is a race condition.

Bill Sheboy

Hi @Martin Flury

Your rule image shows using the Assignee for the Send Email action, but there is no issue within scope at that point in the rule.

The fix is to add a branch to most-recently-created-issue before the email action:

trigger: scheduled
action: create issue for the task
branch: to most recently created issue
- action: send email, changing your email body to now reference {{issue.key}} and {{issue.summary}}

Another way to solve this would be to use the smart value for the email address rather than selecting Assignee from the dropdown in the To field: {{createdIssue.assignee.emailAddress}}

Kind regards,
Bill

All comments

Jack Brickey_h10pa4

Hi @Martin Flury , try adding a re-fetch data action before sending the email? This often times fix similar issues where there is a race condition.

Vishal Biyani_2pr07j

@Martin Flury

You are most probably not using smart values in the right way.

Can you share the screen shot of what you have in email form?

Bill Sheboy

Hi @Martin Flury

Your rule image shows using the Assignee for the Send Email action, but there is no issue within scope at that point in the rule.

The fix is to add a branch to most-recently-created-issue before the email action:

trigger: scheduled
action: create issue for the task
branch: to most recently created issue
- action: send email, changing your email body to now reference {{issue.key}} and {{issue.summary}}

Another way to solve this would be to use the smart value for the email address rather than selecting Assignee from the dropdown in the To field: {{createdIssue.assignee.emailAddress}}

Kind regards,
Bill

Martin Flury_3s1d00

Thanks you very much for your suggestions so far.
I'll check all answers and will give a feedback for sure.

It looks like I have to dive in a bit deeper into this automations, to fully understand the requirements of how it has to be built up. :-)

Martin Flury_3s1d00

@Bill Sheboy you nailed it.

Adding the branch did solve my missing email problem.
After that I got every mail.

Thanks again for your help. Appreciate it.

Martin Flury_3s1d00

Hi @Jack Brickey

I implemented the solution from Bill, which solved my missing email problem.

After adding the "Edit issue fields" action your solution helped me adding this new values to my new email in the step afterwards.

So thank you very much for your help as well.

Martin Flury_3s1d00

I have to admit I'm a greenhorn in Jira automation and the usage of smart values is definitely not one of my strengths.

In this case the adding of a branch solved my original problem and my secondly created problem, having access to the edited field values for the mail, got solved with the re-fetch.

But I'd also like to thank you for your time answering my question.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automations