How do I set the assignee of a sub-task to be a specific assignment member of the parent?

Jon Platt May 29, 2024

I have an automation that is creating a testing sub-task for each bug or enhancement issue. I'm struggling to find a smart value that can set the Assignee of the sub-task to be the Tester of the parent - not the parent assignee.

I've tried every variation of {{issue.parent.Tester}} I can think of, such as value, name, displayName but always get something like Failed to get value for issue.parent.Tester-[User Picker (single user)].displayName: {{issue.parent.Tester-[User Picker (single user)].displayName}}

The full name of the Tester field seems to be Tester-[User Picker (single user)]

Is there an alternative to issue.parent as that doesn't seem to work?

Thanks!

Audit Log.pngAutomation.png

2 answers

0 votes
Nancy Talan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 25, 2024

@Jon Platt  did you ever get this working? I'm trying to do the same thing.

I have automation that creates sub-tasks when the story moves from Open to In Progress. Ideally, when the Tester is set, the sub-tasks that I designate would update to have their Assignee set to the Tester, but it's unclear if I can do that.

So my workaround would be to create the test sub-tasks when the Tester is set, and then set the Assignee of the sub-tasks to the Tester name. 

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 29, 2024

Hello @Jon Platt 

Welcome to the Atlassian community.

When asking for help with an automation rule, it will help us help you if you provide screen images that show the complete rule and the details of each step. Additionally show us the details of the Audit Log for the execution of the rule.

Sometimes problems are related to the context in which the step is executing, which we could determine only if we can see the entire rule.

Also let us know if you are working with issues in a Company Managed project or a Team Managed project.

Jon Platt May 29, 2024

Ticket updated. Thanks

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 29, 2024

Try this.

Next to the Assignee field click the three dots and select COPY

Screenshot 2024-05-29 at 7.38.06 PM.png

 

That will prefill the field with text "Copy Assignee from Current Issue"

Screenshot 2024-05-29 at 7.39.26 PM.png

 

Click on that text and you will get a pop up with two fields; one for selecting the issue from which you want to copy (select Trigger Issue) and the other for selecting the field from which you want to copy data. See if you can find your Tester field in that list.

Jon Platt May 30, 2024

Thanks. I am able to see the Tester field in the list of parent fields but it didn't work. The automation rule ran without generating an error but the Assignee is None. The Tester field in the sub-task is also None but I'm not trying to populate that.

 

Audit Log 1.pngResults.png

 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2024

Please show us new screen images for your rule with the changes you made.

You said you are trying to set the Assignee field on the subtasks, but I don't see the Assignee field in the image you provided for the subtask.

Screenshot 2024-05-30 at 7.27.56 AM.png

Jon Platt May 30, 2024

It's in the screenshot above: Assignee - Copy Tester- from Current Issue but I just changed this to "from Parent Issue" and it still doesn't work.

Automation.png

 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 30, 2024

Yes, I see that in the Automation Rule.

What I am pointing out is that the image of the issue details for the issue the rule supposedly updated does not show the Assignee field. The image you provided is not evidence that the Assignee field did not actually get updated.

Screenshot 2024-05-30 at 4.01.57 PM.png

Jon Platt May 31, 2024

1.png2.png3.png4.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 31, 2024

I advise you to change this to copy from Trigger Issue.

Screenshot 2024-05-31 at 3.39.41 PM.png

Jon Platt June 4, 2024

Thanks for the suggestion. I have done that and still no success. The automation triggers and completes without error but the Assignee remains as "Automation for Jira" instead of the Tester- from the triggering issue.

2024-06-04_10-46-10.png

2024-06-04_10-46-59.png

2024-06-04_10-48-31.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 4, 2024

What is shown in the History for the newly created sub-task? Are there multiple entries for setting the Assignee field?

Prior to the Create Issue step can you add a Log action step, and in that step print the value in the Tester- field into the Audit Log? Use the smart value {{triggerIssue.Tester-}} 

Then run the rule again and show use the Audit Log output.

Like Jon Platt likes this
Jon Platt June 4, 2024

The logged values are correct, so Tester- is a valid reference.

2024-06-04_14-17-56.png

I also inserted a Re-fetch after the Log Action and before the sub-task creation but it didn't make any difference. I'm now researching to see if there is a post-creation step that can assign the sub-task.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 4, 2024

What is shown in the History for the newly created sub-task? Are there multiple entries for setting the Assignee field?

 

Sometimes rules that have been edited many times can end up not functioning correctly.

Have you tried recreating the rule from scratch?

 

Also, you should be able to use a For Branch to shift focus to the recently created (in the rule) issue and then execute an Edit action against it if needed.

Screenshot 2024-06-04 at 2.49.55 PM.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events