Automation / In Progress Epics / Update Points

Jeff Murray March 27, 2024

Hello -

I have created an automation rule to update the Epics points when a value changes for the child (story, task, bug and spike). This works fine.

My question is for Epics already "in progress", can I write a automation rule to update those? 

Thanks,

Jeff

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 27, 2024

Hello @Jeff Murray 

How do you want to update the Epics that are already "in progress"? 

Do you want your first rule to work for Epics that are "in progress"? If so, please show us the details of that rule so that we can determine why it would not be working for "in progress" Epics.

Jeff Murray March 27, 2024

Hi Trudy -

This is what I built. I don't understand how the first rule would update Epics already in progress. Thanks, Jeff

Screenshot 2024-03-27 at 3.36.44 PM.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 27, 2024

Hello @Jeff Murray 

The rule you wrote is intended to change Epics that are not "in progress" to "in progress" when one of their child issues changes from "to do" to "in progress. As written that rule will make no change to an Epic that is already "in progress". There is not need to make a change in that case.

 

From your original post:

My question is for Epics already "in progress", can I write a automation rule to update those?

What update do you want to make to the Epics that are already "in progress"? And what event should trigger that update?

 

Jeff Murray March 27, 2024

Hi Trudy -

I want the current Epics in progress to show the total points of their children. It would basically be a "catch-up" of what has already started. Going forward, my rule written will handle new Epics.

Thanks, Jeff 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 27, 2024

Hello Jeff,

The current rule you showed doesn't show any steps for summing child story points to the parent Epic.

Do you have another rule that does that? Or does the image not show the entire rule?

If you want to do a one-time sum up of child Story points to parent Epics that are already in progress, you could do that with a scheduled or manually triggered rule. Here is an example of Scheduled rule.

Screenshot 2024-03-27 at 3.38.00 PM.png

Screenshot 2024-03-27 at 3.35.36 PM.pngScreenshot 2024-03-27 at 3.35.45 PM.png

Screenshot 2024-03-27 at 3.35.45 PM.png

Screenshot 2024-03-27 at 3.35.45 PM.png

Screenshot 2024-03-27 at 3.35.45 PM.png

Screenshot 2024-03-27 at 3.35.45 PM.png

 

Jeff Murray March 28, 2024

Hi Trudy -

Well...it might help to provide the rule:

 

When: Value changes for story points

Issue is not one of Epics and Initiatives

For: Epic (parent)

Then: lookup issues 

Search for issues using JQL

"parent" = {{issue.key}}

Add: Edit issue fields

story points

Thanks, Jeff

 

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 28, 2024

Hello Jeff,

What value are you using to set the Story points field in the Edit action?

That rule should work for Epics that are "In Progress", since there is no condition that checks the Epic's status.

If it is not working, please share with us the output of the Audit Log from an execution of the rule where you did not get the expected results.

Jeff Murray March 28, 2024

Hi Trudy -

{{lookupIssues.Story Points.Sum}} is the value. Here is the rule and below is the log. I went into a couple of projects (Jira test) and selected a couple of Epics already in progress. Ran the automation in the epic and nothing happened, thanks.

Screenshot 2024-03-28 at 9.31.23 PM.png

 

Screenshot 2024-03-28 at 9.33.58 PM.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 28, 2024

I'm sorry, but your descriptions and the images you are providing from one response to the next don't seem to be aligning.

 

So this last rule for which you have pasted an image is a manually triggered rule that can only be triggered by members of the jira-administrators user group and checks that the issue from which it was triggered is one of a set of types.

Screenshot 2024-03-28 at 2.04.18 PM.png

And you said:

I went into a couple of projects (Jira test) and selected a couple of Epics already in progress. Ran the automation in the epic and nothing happened, thanks.

Running the above rule would require triggering it manually, and if you triggered it from an Epic then the first condition would not be met.

And then the log files show that the rule has not been triggered at all. So it seems like the log file doesn't match the above Manual Trigger rule. Or, as sometimes happens, there is an unexpected delay between the triggering of the rule and the update of the Audit Log display.

 

The rule you described in your previous post in text had a different trigger and different condition:

When: Value changes for story points

Issue is not one of Epics and Initiatives

And again if we review your last post about triggering the rule...

I went into a couple of projects (Jira test) and selected a couple of Epics already in progress. Ran the automation in the epic and nothing happened, thanks.

...the rule you described in text would not be triggered only by changing the Story Points field in the Epic, but then would abort because it the scenario would not pass the condition.

 

 

We need to zero in on one rule, and get images for the current state of that one rule. Then take an action that you think should trigger that one rule. Make sure the action aligns with what is required to trigger the rule, and in an issue in a project that is within the scope of the rule. Then share with us the Audit Log details for that one rule. Please. Thank you.

Jeff Murray April 5, 2024

Hello Trudy -

 

I have resolve my issue.

 

Many thanks for your patience (truly a saint) and understanding.

 

Regards,

Jeff

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events