Automation -Notification email failed due to email not found

[Leslie Hicks]

I have a Assignment rule for when the field value changed in a user picker (custom field) to send an alert to the assigned user in the field.
The rule is failing saying the email was not provided.

[Trudy Claspill]

Hello @Leslie Hicks 

When asking for help with an automation rule it will enable us to help you better if you provide screen images showing

1. The entire rule
2. The details of each step
3. The complete output in the rule log for an execution where the error occurred.

Had the rule ever worked as you expected?

[Leslie Hicks]

It was confirmed in other projects, not successful in this one.

[Trudy Claspill]

The error message indicates that the QA Assigned field had no value. Since the trigger for the rule is Field Value Changed the rule could have been triggered if the field was cleared.

I recommend that you add a condition to confirm that the field is not empty before the action to send the mail.

Also, as per @Bill Sheboy 's question, what type of project does this concern?

[Leslie Hicks]

It is a company managed space. 
Something like this?

[Trudy Claspill]

No, that is not what I suggested 

Remove the three components you added.

Instead click like you did to add those and select "IF: add a condition"

Select the "Work item fields condition"

For Field select "QA Assigned"

For Condition select "is not empty".

Save the changes to the rule.

Try again to make a change to the QA Assigned field. Let us know the results. Share images of the modified rule and the results recorded in the rule execution log.

[Igor Medeiros - Modus Create]

Hi @Leslie Hicks 

Adding to what Bill and Trudy sent, the empty-email error often appears when the rule fires before the user object is committed. A null-check condition on the field plus a Lookup Issues re-fetch usually clears it.

If you'd rather not maintain that workaround, our app Notification Assistant for Jira treats User Picker fields as a first-class recipient type and fires on field-change events without the email-lookup gap.

Feel free to reach out if you'd like to learn more.

[Bill Sheboy]

Hi @Leslie Hicks 

Are you using a team-managed project (TMP) with its People custom field type?  If so, the email address is not available within rules: https://jira.atlassian.com/browse/JSWCLOUD-27793

I recall the possible workarounds are:

1. read the user with the REST API endpoint and the Send Web Request action to get the email address
2. add a global / company-managed user picker field, and use that in the TMP

Kind regards,
Bill