nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copy custom field from child to parent

Molly Hopper

I am trying to create an automation that when a custom field is completed in a child issue (sub-task to a service request, or task to an epic), that same custom field is updated in the parent issue. I've created the rule below, and the log indicates it completes successfully, but the field in the parent issue is still empty and/or the old value. I've tried for: all linked issues, and it fails saying there are not linked issues available.

Is this something that can be done in service management? Any advice for alternative automations would be helpful.

Jira Question.png

Accepted answers

Cristian0791

Hi Molly,

I suggest:

1. When: Value is change ( here you need to select your field)

2.Issuetype = Subtask ( here you specify only for subtasks)

3. For Parent

4. Then: Edit issue fields (here click on the: Copy field from Current Issue and change it to Trigger issue

All comments

Tansu Akdeniz

Hi @Molly Hopper

Welcome to the community.

Instead of "When: Issue updated", you could use "Field Value Changed" trigger to listen only selected custom field change in child. You can also add a condition after the trigger to ensure that the it only runs on the target sub-issues.

Then, in "Edit issue fields" action, choose to copy it from current child issue.

Could you please check it?

Please make sure that you select right issue relation. Ex; Story/Epic has different relation than parent/subs.

If possible, send "Edit issue fields" config and sample issue and audit log.

Cristian0791

Hi Molly,

I suggest:

1. When: Value is change ( here you need to select your field)

2.Issuetype = Subtask ( here you specify only for subtasks)

3. For Parent

4. Then: Edit issue fields (here click on the: Copy field from Current Issue and change it to Trigger issue

Molly Hopper

Thank you! Adding the "trigger issue" part was what seems to have done it.

Dewa

I have similar issues, but the field I tried to edit is custom field.

I use the JSON advanced update : {"fields": {"customfields 13293": "{{"triggerIssue.customfields 13293"}}"}}

but it gave me an error. anyone have the solution?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management