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

Summing up the value of a custom field into the parent issue

Charlie Naylor_hos2hz

Hello,

I have been looking at various posts about using automation to sum up fields into a parent issue, and I just can't get it to work and I am not sure why.

When the automation runs, it sums the parent to 0 regardless as to what I set the children to.

Is anyone able to advise as to what I am missing here?

Thanks in advance

My automation is as below:

Accepted answers

Callum Carlile _Automation Consultants_

Hi @Charlie Naylor , welcome to the Atlassian Community!

Try setting this smart value to {{lookupIssues.customfield_11286.sum}} (I assume this is the custom field ID for your Annual Voice reduction custom field?)

All comments

Callum Carlile _Automation Consultants_

Hi @Charlie Naylor , welcome to the Atlassian Community!

Try setting this smart value to {{lookupIssues.customfield_11286.sum}} (I assume this is the custom field ID for your Annual Voice reduction custom field?)

Charlie Naylor_hos2hz

Hi Callum,
Thanks very much - I tried that too, and it doesn't complete either unfortunately. Anything else I can try?

Callum Carlile _Automation Consultants_

I've just tried this out myself and have replicated what you are seeing with the parent values being set to zero. It seems as though using 'parent' in the lookup will only work when using the 'Parent' branch type, and similarly using "Epic Link" in the lookup will only work with the 'Epic (Parent)' branch type. So:

If you are setting these points on a subtask and want to sum them to the parent issue, you will need to change your branch to just use Parent rather than Epic (parent).

If you are setting these points on a regular issue and want to sum them to the parent Epic, you will need to change your lookup JQL to use "Epic Link" = {{issue.key}}

Rich_xab7ff

@Charlie NaylorI had success using this approach.

Screenshot 2023-04-18 at 10.59.52 AM.png

Charlie Naylor_hos2hz

Works! Thank you

Charlie Naylor_hos2hz

Thanks - I used a different approach that works but that's good to know

Welcome!

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

Quick Links

Find more posts tagged with

automation