Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira automation: Notification to assignee error

Marcel Jünge February 24, 2022

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:
assignee
But 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".  

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 24, 2022

Are you sure the "assignee" the automation is looking at is the assignee of the sub-task?  Is your automation setting the assignee and trying to send the email at the same time?

Marcel Jünge February 24, 2022

First automation: If the issue goes from "Open" to "Planning" specific subtasks are created and assigned.

Second Automation: When the status changes from "Planning" to "In Progress" the subtasks assigness shall be notified via e-mail.

 

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

 

Here are screenshots of both automation rules (Its in german language)First Rule.JPGSecond Rule.JPG

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 27, 2022

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?

Marcel Jünge March 24, 2022

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:

 Error.JPG

Second Rule: 

Second Rule.JPG

Marcel Jünge March 24, 2022

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events