Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with updating child field from parent field

Roman Malynovskyi
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!
September 26, 2024

Hi Community! 
I've probably seen all topics about updating child fields but still have never found the exact situation. 

So I have Parent issue with text fields:

Screenshot 2024-09-26 at 14.05.39.png

Then I've duplicated the same fields to a Child issue:

Screenshot 2024-09-26 at 14.05.47.png

 

Then I created such automation:Screenshot 2024-09-26 at 14.09.04.png

Screenshot 2024-09-26 at 14.09.17.png

But the result is negative:

Screenshot 2024-09-26 at 14.12.37.png

Could you please let me know what I did wrong or maybe missed? 

Because the field names are used only on this project, so I've checked that if I delete them from the Child issue, this problem resolved. But I'm not sure how I would update the exact field then.

And I don't understand why these fields cannot just match but they create second issue - fields are not found.

1 answer

1 accepted

1 vote
Answer accepted
Bill Sheboy
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.
September 26, 2024

Hi @Roman Malynovskyi -- Welcome to the Atlassian Community!

What type of project is this: company-managed or team-managed?  You may find that information at the bottom, left side of the page expanding area.

 

And when you note you "duplicated the same fields to a Child issue", did you add the existing fields to the subtask or create new ones? 

Based on the rule error, it seems you created new fields, and so the rule cannot copy them.  Even though the field names may be the same, if they are new fields, the internal identifier is different and prevents copying them. (i.e., the Sub-task's field cannot be found in the parent, trigger issue configuration)

Also, it appears you may have added a new "Project" field, and there is already a built-in field with that same name.

 

I recommend pausing to first understand if these fields are the same or different between the issue types.  Once that is confirmed, it will be easier to make adjustments to the rule.

Kind regards,
Bill

Roman Malynovskyi
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 4, 2024

Hi @Bill Sheboy 
Thanks for pointing out the creating of the same fields. 
I've deleted duplicates and now automation works! 

Like Bill Sheboy likes this

Suggest an answer

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

Atlassian Community Events