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; } } }

Automation Rule

Casey Enderlein

Hi there - we want to configure an automation rule that automatically populates a custom field for child issues in Jira based on the parent issue setup.

Desired outcome: If child issue is created and parent issue custom field 'intake category' = 'OP', then edit child issue's custom field 'intake category' to = 'OP'.

Can you help guide me with the correct configuration to achieve this automation rule?

Thank you kindly

Accepted answers

All comments

Bill Sheboy

Hi @Casey Enderlein

You may actually want multiple rules for a scenario to copy a field from the parent to a child issue. For example:

When a child issue is created, and has a parent with the field set, copy the field to the child issue
When a child issue edits its parent, and has a new parent with the field set, copy the field to the child issue
When someone manually edits a child issue and changes the custom field, then do ??? For example, perhaps set the field back to the parent value.
When the parent issue edits the custom field, then do ??? For example, perhaps copy the value to any child issues.
etc.

I encourage you to clarify which scenarios you want to address, and then try to create the first rule and test it. Successfully using rules requires learning and experimentation. If you run into challenges, please post an image of your complete rule and audit log details to provide context for the community to offer suggestions.

To get you started on creating your rule, please refer to these documentation and example sources:

Kind regards,
Bill

Casey Enderlein

Thanks, Bill. We want to start with scenario 1 (and then future state iterate upon setup with scenarios 2/3). Here is a screenshot of the rule configuration to attempt at achieving scenario 1; the audit log shows no actions performed when I ran a test (In the test I first created an Epic issue type with the defined intake category > then create a child issue for this epic and the intake category field was not edited to OP).

Bill Sheboy

Thanks for that information, Casey!

When using the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after the trigger. That trigger may fire so quickly that some data may not be available to the rule yet, causing the rule to not work as expected. Please add that action and re-test your rule.

Also, please expand your audit log details with the "Show more" option and re-post the image. That will show the specifics of what happened in the rule steps.

Casey Enderlein

Thanks for the quick reply, Bill. I made the suggested edit (screenshot of updated rule here)

Rule Setup

rule setup.png

I created a new child issue and the audit log says successful (screenshot below), however the child issue's field of intake category did not get edited to 'OP' as we desire (see screenshot below of the child issue and the parent issue)

Audit Log

audit log.png

Parent Issue

Child Issue

Perhaps instead of the rule setup 'editing' intake category for child issue to 'OP' upon creation - is there a way I can achieve just automatically populating this field based on parent issues selection?

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud