Automatically Populating Fields from Parents to Child Issues

Nik Seobaran May 9, 2023

Hi Everyone

Looking for a solution to populate the same fields from the parents to the associated child tickets

We have the Hierachry Initatives > Milestones > Epics > Task/Story > Subtask

When Custom Field "Benefit Value" is updated in Initiative (parent) - I would like this to be populated in the Milestone (Child)

Looking for an Automation Rule solution

1 answer

1 accepted

1 vote
Answer accepted
Mark Segall
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 9, 2023

Hi @Nik Seobaran - You could do something like this:

  • TRIGGER: Field Value Changed (Benefit Value)
  • CONDITION: Issue Type = Initiative
  • BRANCH (JQL)
    • "Parent Link" = {{Issue}}
    • ACTION: Edit Issue (Benefit Value)
      • Copy from Trigger Issue
Nik Seobaran May 9, 2023

Hi Mark

 

Thanks for this

I made the changes - shows success - yet the field is not actually updated

Screenshot 2023-05-09 at 15.38.06.png

Mark Segall
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 9, 2023

Hmm - Can you please show a screenshot of the Edit Issue Fields component?

Also... What type of field is Business Value?

Nik Seobaran May 9, 2023

Screenshot 2023-05-09 at 20.43.37.pngScreenshot 2023-05-09 at 20.43.05.pngScreenshot 2023-05-09 at 20.42.53.pngScreenshot 2023-05-09 at 20.43.24.png

Nik Seobaran May 9, 2023

Business value is a multi-select drop down

Mark Segall
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 9, 2023

Your screenshot shows Copy from Current Issue.  It needs to be Copy from Trigger Issue

Nik Seobaran May 9, 2023

something like this

{
"fields": {
"customfield_11636": "{{triggerissue.customfield_11636.id}}"
}
}

Nik Seobaran May 10, 2023

Actually got it working now - I did not know you can change the "Current Issue"

Like Mark Segall likes this
Chris Dail May 1, 2024

Is there a way for this to trigger immediately when the user is creating the issue (before saving).  The reason is that some fields are required, so it defeats the purpose for this to fire after saving.

Thanks!

Suggest an answer

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

Atlassian Community Events