Parent assignee auto-assigned to children upon linking - can't make this rule work

[Aiste Marija Aidukaite-Urbanovic]

Hi! I've been trying to build a rule that would let me automatically copy the assignee from the parent issue. But it doesn't work, and for the life of me, I have no idea why. Currently, for testing purposes, I've built it so that the trigger is manual. ATSV3-1 is my parent issue, which has an assignee, and ATSV3-8 is the child issue, which has a parent and no assignee, that I'm trying to get to copy the assignee from the parent via automation. I'm running the rule from the ATSV3-8. I'm attaching a few screenshots. I'm using the cloud version of Jira Service Management. And yes, I'm using Edit issue fields action - Assignee > Copy from parent. Hope someone here can give me some guidance. Ty  

[Calvin]

I may be misunderstanding here, but I don't see why you need the branch at all? In ATSV3-8, just use "edit issue field" that you have, pick the assignee value, and "Copy Assignee from Parent".

At the moment, it looks like your jumping into the parent ticket, and then editing that one?

[Aiste Marija Aidukaite-Urbanovic]

Hi Calvin, that makes sense. I tried something else already too, but that doesn't work either. It seems similar to what you suggest. Is there a reason why I can't use Assign the issue to and need to specifically use Edit issue fields? Because mine still doesn't work. 

[Aiste Marija Aidukaite-Urbanovic]

I have tried your recommendation, unfortunately doesn't work - any ideas what I'm doing incorrectly?

My trigger issue clearly has a parent issue, which in turn has an assignee. Still the error seems to be that it can't find an issue to copy from. I'm so lost at this point, this seems to be way harder than it should. That's the reason tbh why I tried branching.

[Bill Sheboy]

Hi @Aiste Marija Aidukaite-Urbanovic -- Welcome to the Atlassian Community!

To copy the field from the parent, use that option in the edit: "Copy from parent".  That will use the built-in parent / child relationship for issues.  For example, between and Epic and Story.

However what you show is "issue linking" and not the built-in parent / child relationship.  When you want to identify the issue by linking, that would need to use the key directly to find the assignee.

Kind regards,
Bill