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

Smart Value to display the sum of child issues linked to an epic

carolina_z15ajl

Hello,

I'm trying to display the total number of child issues linked to an epic on a custom field in the Epic.

I created an automation that would auto-populate a custom field called "number of child issues linked", but I can't get it to calculate the total sum of this count.

Here's my rule:

Screenshot 2023-03-27 at 11.49.44.png

I believe the issue is with the Smart Value I'm using {{issue.size}}, it's not counting the total number, it's just displaying the number "1" when I make an update to any child task issues. For eg: I have 4 tasks that are child issues to an epic, I update all the tasks to my automation runs, and my custom field in the Epic (number of child issues linked) displays there is only 1 child issue linked.

I've also tried the {{lookupIssues.size}} smart value and it always returns 0.

Any ideas of what could work?

Accepted answers

Trudy P Claspill

Hello @carolina

{{lookupIssues.size}} should give you the number of issues returned by the JQL in the Lookup Issue action.

You can use the Log action to print messages and smart values into the rule's Audit Log to help with debugging the rule.

Can you change the Edit action to use {{lookupIssues.size}}, and some Log actions to print out each smart value, then take an action again to trigger the rule? After that share with us the Audit Log details for that execution of the rule.

It would also be helpful if you can show us the parent Epic details to show us the Child Issues section to affirm how many child issues exist in the Epic.

Lastly, why have you opted to use the Issue Updated trigger? That will cause the rule to be triggered for every type of update for the issue. Do you really want it triggered that frequently?

All comments

Trudy P Claspill

Hello @carolina

{{lookupIssues.size}} should give you the number of issues returned by the JQL in the Lookup Issue action.

You can use the Log action to print messages and smart values into the rule's Audit Log to help with debugging the rule.

It would also be helpful if you can show us the parent Epic details to show us the Child Issues section to affirm how many child issues exist in the Epic.

Lastly, why have you opted to use the Issue Updated trigger? That will cause the rule to be triggered for every type of update for the issue. Do you really want it triggered that frequently?

carolina_z15ajl

Hi @Trudy P Claspill thank you for your reply! I changed the Edit action to use {{lookupIssues.size}}.

I've been doing some research on the Log Action, but I can't figure out what I need to write as the log message I'm new to the game. Do you have any tips?

Here's what the Epic looks like:

Screenshot 2023-03-28 at 09.22.27.png

You can see that to the right I have a field to display the number of child issues, which should be 2, but it's 0.

Trudy P Claspill

For Log Action you can put in plain text and/or smart values. So, for instance, after the Lookup Issues action you could use a Log action to print out the size of the results set:

Lookup Issues returned this many issues: {{lookupIssues.size}}

You can use the Log action to print out any smart value to check that the value contains what you expect.

Can you show us the output of the Audit Log for the rule when it executes? Click on Audit Log above the rule steps. That will show you the logs for each configuration change and execution of the rule. You can click on the Show more to the right of an entry to get more details.

Looking at the rule details you provided and the image of the Epic with child issues I see a problem. In the Epic it looks like the child issues might all be Bugs based on their icon. In the rule you have a condition to check that the issue that triggered the rule (the issue that was changed) is a Task. As this Epic doesn't appear to have any Task child issues, the rule will not update this Epic.

carolina_z15ajl

Hi Trudy,

Thank you so much for your reply! Your comment is correct, I sent you a picture of only bugs when the rule was meant for tasks by mistake.

The audit log came back as zero again and ticket 124 has 5 child tickets linked.

Screenshot 2023-03-29 at 08.57.19.png Screenshot 2023-03-29 at 08.58.14.png

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-software

jira-software-cloud