JSON help with automation of field Team

Karolina Yeong
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!
February 10, 2025

I've been trying to set an automation for field Team that is used by advanced roadmaps. I want to automatically set child issue Team to be same as Parent. With below JSON code the automation runs successfully, but the issue field is not being populated.

{ "fields": { "customfield_10001": "{{issue.parent.customfield_10001}}" } }

 

In my automation I have also included a log to see if the parent Team is read OK, and the log shows: Parent Team value: d458a753-47c4-4fde-ae80-63304af11702.

I also tried to directly enforce above Team to the issue being created but this also ends up in field not being populated. How can I force the child issue field to populate?

3 answers

1 accepted

2 votes
Answer accepted
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.
February 10, 2025

Hello @Karolina Yeong 

Welcome to the Atlassian community.

Is this you current rule?

example.png

If so, this will not achieve your goal.

With the branch "For Parent" you are shifting the focus of the rule from the trigger issue to the Parent of the trigger issue. Actions that you take inside of the branch will affect the Parent issue, not the trigger issue. Within the branch use of the {{issue}} smart value will refer to the Parent issue, not the trigger issue.

You initially said you had a rule that included the Log action to print the value of the Team field. Can you revert to that version of the rule and show that to us?

Karolina Yeong
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!
February 10, 2025

This is what I have now: example2.png

the log returns: Parent Team value: d458a753-47c4-4fde-ae80-63304af11702

Karolina Yeong
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!
February 10, 2025

@Trudy Claspill the suggestion of removing the branch seems to have done the trick! I was trying to use the Jira AI assistant and this is where the branch had come from :)

0 votes
Vishal Biyani
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 10, 2025

@Karolina Yeong 

In the edit issue field, you can use copy Teans from parent. You may not need to branch to parent as long as it is ensured parent has Teams field populated

Karolina Yeong
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!
February 10, 2025

@Vishal Biyani  I've updated my post with latest findings. I can run automation OK now, but the field isn't being populated on trigger issue.

0 votes
Karolina Yeong
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!
February 10, 2025

This is what I have so far:

When a child issue is added to parent, I want the child issue to inherit Parent's Team. example.png

Suggest an answer

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

Atlassian Community Events