automation rule - copy reporter to be assignee of sub task created
Asked by eric caprio:

I have an automated flow for when a sub-task Code Review is automatically completed through another automation of Pull Requst Merged. Details below and screenshots - Problem: the copy of reported in the parent task is not making it to the new sub-task QA

- it closes the sub-task code review and creates a sub-task QA

- moves along parent story to QA

- supposed to assign the reporter from parent task to be the assignee of the new sub-task QA

![screencapture-darwin-cx-atlassian-net-jira-settings-automation-2024-09-24-16_03_34.png](https://community.atlassian.com/t5/image/serverpage/image-id/349081iC6E85238801468C7/image-size/large?v=v2&px=999 "screencapture-darwin-cx-atlassian-net-jira-settings-automation-2024-09-24-16_03_34.png")


Answers:
author: Shawn Doyle - ReleaseTEAM
body: It looks like you are approaching it correctly, I tested it on my cloud instance and that works as expected. If it just won't work for you, try one of these other approaches. I have heard of some race conditions, where sometimes the child doesn't know it's parent in this case, and that putting a delay in the automation would address this, however, I have not personally run into that.

You could use the Clone Issue step and only select the reporter field. However if the first approach isn't working, I would be skeptical that this wouldn't have the same issue.

Or create a new Automation that triggers off the creation of your subtask QA, then it checks the reporter field and updates it if incorrect. This would avoid any issue with the subtask not understanding it's parent yet.

comments: author: eric caprio
body: Thank you Shawn, I will attempt adding another automation rule to check reporter field and updates.


author: Trudy Claspill
body: Hello [@eric caprio](/t5/user/viewprofilepage/user-id/5547489)

What is the information that you get in the rule execution log when the rule runs and the subtask is created?

comments: author: eric caprio
body: Action details:

<br />

Transition issue  
Transitioned issues to  
QA

<br />

Edit issue  
Issues edited successfully  
INV-718

<br />

Create issue  
**Can't find issue to copy from**   
**assignee**   
Issues created successfully  
INV-794

<br />

Issue condition  
The following issues did not match the condition:  
INV-794

<br />

The following issues passed:  
INV-791

Transition issue  
Transitioned issues to  
Done

Associated items:  
Pull request merged  
INV-718,  
INV-718:marketing campaign preview information  
Create issue  
INV-794  
Branch rule / related issues  
INV-791,  
INV-794


author: Trudy Claspill
body: To what value is the Assignee field in the subtask being set?

Is the Reporter of the parent issue among the users that have the Assignable User permission in the project?

Who is the actor of the rule? Does the actor of the rule have the Assign Issues permission in the project?


author: eric caprio
body: Assignee is being set to "Copy from Reporter from Parent Issue".

Yes, reporter has same permissions - I can go assign them manually after the case.

Actor of the rule is the below:

![Screenshot 2024-09-25 at 12.00.16?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/349309i25DF5A5FB90019F7/image-size/large?v=v2&px=999 "Screenshot 2024-09-25 at 12.00.16?PM.png")

I have tried out the other response solution of another automation rule that when a sub-task QA is created, if assignee is empty, set assginee as Copy from Reporter from Parent Issue


author: Trudy Claspill
body: I was unclear with my first question. What I meant was, what is the actual value that you end up seeing in the sub-task Assignee field after this rule completes?


author: eric caprio
body: it is set to unassigned. Which I assume is empty.


author: Trudy Claspill
body: Did the solution of a second rule work for you?

I think [@Shawn Doyle - ReleaseTEAM](/t5/user/viewprofilepage/user-id/815120) is on track by saying there might be a race condition.


Tags: cloud

jira-cloud