We have a JIRA Automation in Place as below.
Trigger: Epic status is changed to "Ready for Approval"
Additional IF conditions are checked.
There's a multi-select custom field called "Impacted Units".
Based on the selections to the above field x number of task are to be created and assigned to each Unit Manager.
The Tasks are getting created successfully. e.g if there are 3 "Impacted Unit" then 3 child Tasks are created. However, when we try to assign the issue, instead of setting the assignee on the created Task, the automation script sets the assignee on the "Trigger Issue".
As the "For Each" action is running in a branch, it should ideally set the Assignee on the issue created inside this branch.
Any suggestions/ ideas would be appreciated.
Hi @Aslam Mohammed ,
Sorry if I understood it wrong but why don't you set the Assignee field in the "Create new Task" step?
We are checking the values in the custom field and running the "For Each" action for the selected values to determine how many tasks are to be created.
e.g if this field has values UK, AU, NZ then 3 Tasks are created. And for each task the assignee needs to be a different user.
So, assigning the Task at creation stage is possible, however the automation script simply creates the tasks based on the for loop and can't validate the Impacted BU during task create action.
If it can do this, it would be ideal. Any suggestions welcome.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would add another Automation which works on "Issue created" in scope of "Chart of Account" (which should be triggered from another automation) and set the assignee there, depend on the value.
Because you are trying to use "Assign" operation which only focuses on the trigger issue wherever you place it in the automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Salih Tuç tried that already but it never picks these new tasks created by Automation to update the Assignee.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the new automation, did you mark this checkbox?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Salih Tuç this seems to have worked, after I selected this check-box on the second set of automation rules. Thanks a lot for the guidance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Happy to hear that, please don't forget to accept the answer if it worked for you :)
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.