I am trying to create an automation between two projects. The current JIRA hierarchy we follow is as below; Portfolio Epic > Epic > User Story/Task Problem Statement: I have two projects Project A and Project B * Project A - Portfolio Epic* Epic 1 * Epic 2 * Epic 3 * Project B - Portfolio Epic * Epic 1 * Epic 2 * Epic 3 I have an Epic in Project A - Epic 1 that is linked via "Related To" link to the overall Portfolio Epic in Project B. Both projects have two different project keys. I am trying to set up an automation that looks at Epic 1 (Project A) and based on the "Relates To" link picks up the children in Project B - Portfolio Epic and sums up the story points and the % complete on children tickets and writes it back to Project A - Epic 1. What I have got so far: Currently the Automation is manually triggered while I test it out and I will move it to scheduled or auto triggered once I have it to where I need it. Story points is calculated using the following - {{lookupIssues.Story Points.sum}} At this point although the above rule is supposed to work it returns no value as I suspect the following may be blocking it. This automation only works if the rule is global; as project specific rules restrict the look up clause above. I need help validating my theory. Second part to my problem is that I am unable figure out if there is a way to get the progress % over to Project A - Epic 1 from Project B Any help and/or guidance would be greatly appreciated.

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 - calculate progress based on children of linked epics

kenneth.gomes

I am trying to create an automation between two projects. The current JIRA hierarchy we follow is as below;

Portfolio Epic > Epic > User Story/Task

Problem Statement:

I have two projects Project A and Project B

Project A - Portfolio Epic
- Epic 1
- Epic 2
- Epic 3
Project B - Portfolio Epic
- Epic 1
- Epic 2
- Epic 3

I have an Epic in Project A - Epic 1 that is linked via "Related To" link to the overall Portfolio Epic in Project B. Both projects have two different project keys.

I am trying to set up an automation that looks at Epic 1 (Project A) and based on the "Relates To" link picks up the children in Project B - Portfolio Epic and sums up the story points and the % complete on children tickets and writes it back to Project A - Epic 1.

What I have got so far:

JIRA Automation 1.PNG

Currently the Automation is manually triggered while I test it out and I will move it to scheduled or auto triggered once I have it to where I need it.

Story points is calculated using the following - {{lookupIssues.Story Points.sum}}

At this point although the above rule is supposed to work it returns no value as I suspect the following may be blocking it. This automation only works if the rule is global; as project specific rules restrict the look up clause above. I need help validating my theory.

Second part to my problem is that I am unable figure out if there is a way to get the progress % over to Project A - Epic 1 from Project B

JIRA Automation 2.PNG

Any help and/or guidance would be greatly appreciated.

Accepted answers

Bill Sheboy

Hi @kenneth.gomes

Your hypothesis is correct about the rule scope: a lookup issues action (or branch, etc.) can only see the issues within the selected scope of the rule.

Next regarding the % progress...first how do you want to measure progress? The image you show is of a parent and child issues. That progress indicator is by the status category of issues. There are other ways to measure progress, such as based on the aggregate of your estimation values.

Once you have selected your progress method, you could use the issues in the lookup issues and smart value list filtering (or separate lookup calls) to compute the result.

Kind regards,
Bill

Mark Segall_iqztfr

Hi @kenneth.gomes - You are correct that this needs to be a multiple project rule scope to span across your two projects. Once the scope is updated, you should have no issue with your second problem.

Be warned though that Relates To is a nasty link type when you're trying to automate because there is no "parent/child" relationship as you have with Blocks/Is Blocked By and Clones/Is Cloned By link types. This could cause some pain points in your automation.

All comments

Bill Sheboy

Hi @kenneth.gomes

Your hypothesis is correct about the rule scope: a lookup issues action (or branch, etc.) can only see the issues within the selected scope of the rule.

Once you have selected your progress method, you could use the issues in the lookup issues and smart value list filtering (or separate lookup calls) to compute the result.

Kind regards,
Bill

Mark Segall_iqztfr

Hi @kenneth.gomes - You are correct that this needs to be a multiple project rule scope to span across your two projects. Once the scope is updated, you should have no issue with your second problem.

kenneth.gomes

Thank you for helping me validate my theory

kenneth.gomes

Hi Bill,

Could you point me to the function that would help me aggregate the estimation values?

Bill Sheboy

Certainly! Here are a couple of examples, using the math functions and smart value list filtering, with references below...

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/

https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588

For the same percentage the parent/child shows based on count:

{{#=}}ROUND((0+{{#lookupIssues}}{{#if(equals(status.statusCategory.name,"Done"))}}1+{{/}}{{/}}0)/{{lookupIssues.size|0}}*100,0){{/}}

To instead do this by story points, try this:

{{#=}}ROUND((0+{{#lookupIssues}}{{#if(equals(status.statusCategory.name,"Done"))}}{{Story points|0}}+{{/}}{{/}}0)/{{lookupIssues.Story points.sum|0}}*100,0){{/}}

How these work...

using a lookup of all of the issues
first use smart value list filter to find the ones with a Status Category of done; for those items, add a value followed by a plus sign
the above value is wrapped in parenthesis, so it can be divided by the total for the entire lookup result
that value is then multiplied by 100 and rounded so it appears as a percentage, 0 to 100
finally everything is wrapped in the math operators
note inside of the rounding operation...an extra "0+" and trailing "0" are added. This handles the case when the lookup returns nothing.

kenneth.gomes

Hi Bill,

I got access to run the rule globally but for some reason the story points are not being summed up. I haven't used your formula yet but instead I tried to keep it simple by using {{lookupissues.Story Points.sum}} but the automation still wont sum up the story points.

Log

JIRA Automation 3.PNG

Based on the automation it is able to pick up the linked PE but it is unable to sum up the epics underneath it.

CL - 6372 is a Epic

UIP-6 is a Portfolio Epic

I am trying to sum up the child issues underneath them.

JIRA Automation 4.PNG

Any suggestion or help would be greatly appreciated.

Thanks

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

automation