Im hoping to get some help. We have a custom field (customfield_12971) that is used at two different ticket hierarchies. Initiative and Feature Level. We leverage this field for statuses (in a string format). What I want to do is roll all the child inputs of customfield_12971 into a singular output in the parent customfield_12971. So essentially if there were 3 child tickets with statuses like the below: Child 1 (customfield_12971) is: * Status is blah blah Child 2 (customfield_12971) is: * Status is ABC Child 3 (customfield_12971) is: * Status is 123 Then the parent (customfield_12971) would be: * Status is blah blah * Status is ABC * Status is 123 Note: this would be an automated push (happening weekly) so Im not too worried about syncing it up as a singular child ticket is updated (although that would be ideal) I have a rule set up and it says it is successful but the info isnt populating in the parent at all. I suspect its because there are multiple children, any workarounds? Thanks in advance!

Hi @Travis Hill First thing, what version of Jira are you using: Cloud, Server, or Data Center? That impacts how to solve this for the different versions of automation features. For example, with Jira Cloud, the Lookup Issues action could be used to access the custom field and gather the results: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues * trigger: scheduled weekly, with JQL to find the parent issues * action: lookup issues, with JQL to find the children of a specific parent from the trigger * smart value condition: check if there were results found from the lookup* first value: {{lookupIssues.size}} * condition: greater than * second value: 0 * action: edit issues, to update the parent with the child information, adjusting this based upon the type of your custom fields {{#lookupIssues}} * {{customfield_12971}} {{/}} This would not work for Data Center version as Lookup Issues does not support custom fields yet. Instead a call to the REST API would likely be needed: https://community.atlassian.com/t5/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/bc-p/2883071#M16701 Kind regards, Bill

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

Status Rollup Jira Automation

Travis Hill_08pum3

Im hoping to get some help. We have a custom field (customfield_12971) that is used at two different ticket hierarchies. Initiative and Feature Level. We leverage this field for statuses (in a string format). What I want to do is roll all the child inputs of customfield_12971 into a singular output in the parent customfield_12971.

So essentially if there were 3 child tickets with statuses like the below:

Child 1 (customfield_12971) is:

Status is blah blah

Child 2 (customfield_12971) is:

Status is ABC

Child 3 (customfield_12971) is:

Status is 123

Then the parent (customfield_12971) would be:

Status is blah blah
Status is ABC
Status is 123

Note: this would be an automated push (happening weekly) so Im not too worried about syncing it up as a singular child ticket is updated (although that would be ideal)

I have a rule set up and it says it is successful but the info isnt populating in the parent at all. I suspect its because there are multiple children, any workarounds? Thanks in advance!

Screen Shot 2024-12-13 at 4.30.59 PM.png

Accepted answers

Bill Sheboy

Hi @Travis Hill

First thing, what version of Jira are you using: Cloud, Server, or Data Center? That impacts how to solve this for the different versions of automation features.

For example, with Jira Cloud, the Lookup Issues action could be used to access the custom field and gather the results: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

trigger: scheduled weekly, with JQL to find the parent issues
action: lookup issues, with JQL to find the children of a specific parent from the trigger
smart value condition: check if there were results found from the lookup
- first value: {{lookupIssues.size}}
- condition: greater than
- second value: 0
action: edit issues, to update the parent with the child information, adjusting this based upon the type of your custom fields

{{#lookupIssues}}
* {{customfield_12971}}
{{/}}

This would not work for Data Center version as Lookup Issues does not support custom fields yet. Instead a call to the REST API would likely be needed: https://community.atlassian.com/t5/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/bc-p/2883071#M16701

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Travis Hill

First thing, what version of Jira are you using: Cloud, Server, or Data Center? That impacts how to solve this for the different versions of automation features.

trigger: scheduled weekly, with JQL to find the parent issues
action: lookup issues, with JQL to find the children of a specific parent from the trigger
smart value condition: check if there were results found from the lookup
- first value: {{lookupIssues.size}}
- condition: greater than
- second value: 0
action: edit issues, to update the parent with the child information, adjusting this based upon the type of your custom fields

{{#lookupIssues}}
* {{customfield_12971}}
{{/}}

Kind regards,
Bill

Travis Hill_08pum3

@Bill Sheboy we are in cloud I believe!

Travis Hill_08pum3

@Bill Sheboy that is helpful but I think the problem would be that I need to do this for several hundred tickets at a time and they dont have specific JQL other than them just being the same ticket type basically.

Also, with lookup issues isnt it only 100 at a time? We would exceed that I believe.

Bill Sheboy

Backing up a bit: what problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help reveal other solution approaches.

Until we know that...I will try to answer each part of your post, so please let me know if I miss something...

I need to do this for several hundred tickets at a time

When a rule needs to update many issues, it helps to use a Scheduled Trigger with a JQL statement which can exclude issues that have already been processed (i.e., the "stopping criteria"), such as checking if a field is empty or a custom field to indicate the "last updated date / time by my rule". This would be the "stopping criteria". Without that, the rule will repeatedly process the same issues.

they dont have specific JQL other than them just being the same ticket type basically

The JQL for the trigger could be quite simple, perhaps just the issue type, although it still needs some form of "stopping criteria", as described above.

Also, with lookup issues isnt it only 100 at a time?

That is correct. The Lookup Issues action can process a maximum of 100 issues, as the action relies on the REST API endpoint which has that limit.

The Scheduled Trigger has a higher limit, but the combined impact of the trigger and rule actions such as Lookup Issues could exceed other limits. Please look here to learn more: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

Welcome!

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

Quick Links

Find more posts tagged with

automation

jira-automation

cloud-automation