Jira automation: Notification to assignee error

Question

Hi,

i have a question: In our jira service management project i created an automation rule: When the subtasks status change from "Planning" to "In Progress" an notification shall be send to the assigned user (users get assigned automatically to the subtasks).

But there is an exception: One specific user that has tasks assigned to him shall NOT receive a notifcation.

Jira automation shows me an error when trying to execute the automation rule:

There is no value set for the field:assigneeBut the assigness are set automatically (via automation rule) for the subtasks. Any idea what the problem is here?Summary: I want subtasks assigness to get a notification with exception of one assigne that  shall not receive a notification. All subtasks assigness are set automatically when the subtask status changes from "Planning" to "In Progress".

Marcel Jünge · Answer

But the rule seems to be correct because when i change "Assignee not" to "Assignee is" it works and all assigness get notified....

Marcel Jünge · Answer

Sorry for my delayed reply. Im very busy at the moment...

First Rule: When the issue goes from status "Open" to "Planning": Subtasks are created and assigned --> That works

Second Rule: When the Issue goes from "Planning" to "In Progress": The subtasks assignees that were assigned in the previous rule shall be notified except for a specific assignee

Error:

Second Rule:

Nic Brough -Adaptavist- · Answer

Ok, I'm a bit confused on one point.  Are the assignees on the sub-tasks set with the first automation or the second?

"First automation: If [...] specific subtasks are created and assigned."

"So the subtasks are assigned when the second rule is executed"

My other clarification is on the second rule (I'm afraid my German is almost non-existent, so I don't know if I am translating anything well enough) - it looks like the trigger is "when issue goes from planning to in-work", and then it tries to iterate through the sub-tasks, but I have a feeling the assignee it is looking at (Assignee ist nicht) is the assignee for the issue that changed status, not the sub-tasks.  Does that seem to be what is happening?