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

JIRA Automation - Assign Created Issue Not Working as expected

Aslam Mohammed

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.

Screenshot 2024-11-15 225939.png

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.

Accepted answers

Salih Tuç

Hi @Aslam Mohammed ,

Sorry if I understood it wrong but why don't you set the Assignee field in the "Create new Task" step?

Screenshot 2024-11-16 021112.png

All comments

Salih Tuç

Hi @Aslam Mohammed ,

Sorry if I understood it wrong but why don't you set the Assignee field in the "Create new Task" step?

Screenshot 2024-11-16 021112.png

Aslam Mohammed

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.

Screenshot 2024-11-15 231443.png

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.

Salih Tuç

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.

Aslam Mohammed

@Salih Tuç tried that already but it never picks these new tasks created by Automation to update the Assignee. Screenshot 2024-11-15 233151.png

Bill Sheboy

Hi @Aslam Mohammed

In your original rule, the assign action will not work because branches cannot be nested (to allow branching to the most recently created issue).

What is the source of your assignee?

If it is from a field from the trigger issue, the assignment could happen when the issue is created by referencing that field as a smart value. There is no need for two automation rules for this scenario.

Kind regards,
Bill

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