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 Parent to child

Nelson Nittala

Hi,

I am trying to copy custom field from parent (Epic) to child (Story, Task). When using Jira automation, it is getting Throttled as the number of children retrieved are more than limit. I have split the query, but still exceeding the limit.

I am new to Scriptrunner. Can someone help me how to achieve above using Scriptrunner Query? If there is a reference, please send me the link. I am using Jira cloud premium license. Thanks.

Accepted answers

Nelson Nittala

Also, this is One time update I am trying to execute in a project. I have a jira automation rule setup to run when issue is created/updated going forward.

All comments

Nelson Nittala

Also, this is One time update I am trying to execute in a project. I have a jira automation rule setup to run when issue is created/updated going forward.

Trudy P Claspill

Hello @Nelson Nittala

Can you show us the Automation Rule you tried to use?

Which limit are you exceeding with the Automation Rule?

To get the child issues:
- Are you using a JQL in a Scheduled trigger?

- Are you using a Lookup Issues actions?

- Are you using a Branch For Child Issues?

Nelson Nittala

Using JQL in a scheduled trigger to retrieve all EPICS and updating custom field on Story and Task children.

Nelson Nittala

my jql on the trigger is

project = ABC and issuetype = Epic

Trudy P Claspill

How many child issues does each Epic have? Are there other type of child issues per Epic besides Story and Task?

The limit on branching for issues is 150. I see that you have a condition within the branch to limit the change to Task and Story type issues. You could incorporate that into the Branch to reduce the number of issues being retrieved for the branch:

Use a Related Issues / JQL branch instead of a Related Issues / Children branch.

Screenshot 2025-07-08 at 12.26.58 PM.png

Are you trying to overwrite content, or fill a currently blank field, or both? If you are trying only to fill blank fields then you could add that the the JQL criteria to further reduce the number of issues retrieved in the branch.

Since you say you also have a rule to handle this copy for newly created issues, you could add that to the above JQL criteria also to exclude issues with a Created value newer than the date that other rule was enabled.

Will that reduce the child issues per Epic to 150 or less?

How many Epics are you processing?

There is another overall limit to the number of issues a rule can fetch and the limit is 5000. That would be the number of Epics fetched in the trigger plus the total number of child issues retrieve in the branch for each Epic.

You could also add a label to each Epic after the branch to indicate processing for that Epic is done, and then incorporate the absence of that label into the JQL in your trigger for selecting Epics.

Vishnu Vardhan

Hi @Nelson Nittala

Hope you doing well!

You mentioned that the automation rule was throttled, which means the automation execution limit has been exceeded.

In the Jira Premium subscription, you are allowed 1,000 rule executions per user, per month.

Your automation rule is currently set to run every 5 minutes, which quickly consumes the available execution quota.

Best Regards,

Vishnu Vardhan

Nelson Nittala

Hi Vishnu, it is just a testrun in my sandbox and configured 5 min for a quick test. After that I disabled it. But I see jira limitations in processing. If jira has limitations are there any other options?

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