Forums

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

How to enable auto population of child metadata from parent

James Farley
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!
May 22, 2024

I've created a 'select from list' field that's associated to all issue types, and populated that field for epics.  

I'd like to automate the inheritance of that value to all child issue types (both where the relationship already exists, and also when new 'child' links are created in the future).

I only wish for this info at levels '1' & '0' (Epic and 'story/task/bug').

(I did try searching for similar questions in this community, but was surprised to come up empty... really appreciate any help offered)

Presumably I'll need 2 rules -> one disposable one to treat the existing work items (manually triggered?), and another triggered whenever the link is made to an epic? 


----
For extra context, this field is to specify what client the change relates to, and there are 10-15 options.

I was able to work out how to update children to a specific client when the parent 'client' field is updated, but the action I want is to inherit whatever value is entered for the parent (rather than assume that any update means the child should be marked as 'client x')

1 answer

0 votes
Kalyan Sattaluri
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.
May 22, 2024

Hello @James Farley 

Yes, you are correct. You will need 2 rules.

1 rule to handle existing values. Best is to have a scheduled trigger and take care of all issues at once. Another rule for field change on Epic.

Your rule #2 will be:

  • Trigger = Field Value change -> Select your field
  • Branch, choose JQL option -> give JQL as: Parent = {{key}}
  • Then Edit Issue -> Choose field from drop down, select 3 dots to the right, choose copy from Trigger issue.

Your rule #1 will be:

  • Trigger = Scheduled with JQL and give JQL -> "thisfield" IS NOT EMPTY
  • Note, you can disable after this rule is run once.. Next steps are same..
  • Branch, choose JQL option -> give JQL as: Parent = {{key}}
  • Then Edit Issue -> Choose field from drop down, select 3 dots to the right, choose copy from Trigger issue.

Please author and try, share rule screenshots and audit log if issues..

Hope it helps, Thanks!

James Farley
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!
June 4, 2024

Thanks Kaylan 🙏

Suggest an answer

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

Atlassian Community Events