Automation Rule to Create multiple subtasks

[Nathan Arnott]

I am creating a manual trigger rule that should create 2 subtasks. 

The first subtask sets the Assignee to "Copy from Parent"

The second subtask sets the Assignee to a particular user: "John Doe"

When the rule runs, it creates the 2 subtasks, but both are assigned to the parent Assignee instead of the second subtask being assigned to John Doe. Seems like a bug, but am I missing something?

[Nathan Arnott · Accepted solution]

Looks like our previous Jira administrator put in a custom Post function in the Subtask workflow for setting the assignee on creation. That would explain the wierd results.

Thanks @John McKiernan and @John Funk for your help.

[John McKiernan]

Ah yes that makes sense! Glad you got it sorted :) 

[John Funk · Accepted solution]

Hey Nathan,

Can you provide a screenshot of your rule?

[Nathan Arnott]

Here it is.

[John Funk]

Maybe @John McKiernan can help explain why it doesn't work in the second sub-task. I have seen that happen with others before. 

In the meantime as a quick fix, you might try adding a Branch Rule/ Related Issues component at the end and use Most recently created issue. 

Then add an Edit issue component and update the Assignee field to you. 

Be sure to take out the Assignee field from the create though (although I don't know that it would affect anything to take it out. 

[Nathan Arnott]

That workaround worked. Thanks. Would love to see this work as expected though :)

[John McKiernan]

Hey @Nathan Arnott ,

That is a strange one. I just copied your rule exactly and all worked as expected on my side. 

It's possible that automation is going a little quicker than Jira. You could add a 'refresh issue data' action before your second sub-task to add a delay or as John suggested that branch would do the job. I'll check with an engineer to see if there is anything odd going on but glad that it is working for you now at least!

Cheers,

John 

[Nathan Arnott]

@John McKiernan I just tried the refresh approach, but it didn't work. It still left both subtasks assigned to the parent assignee.

I tried setting both creation rules to set Assignee to "Unassigned" as a test, yet both are set to the Assignee on creation. I'm starting to suspect that our previous Jira administrator may have set up some other kind of automation that is doing this. I'll do some more digging and see...