Automation issue

[Max]

I have created the rule and it works just fine.

My Story Point estimation counts on the Task (from the sub-tasks).

Have a look:

The problem is the following:

I want to edit this rule and add here the conditions to calculate the Story Points for the Epics (from the tasks...that should belong to the Epic).

This is how I want to edit the existing rule:

So I've edited the same rule like this:

next step:

but the counting not working for the Tasks

have a look:

Kindly help me here ^_^

[Trudy Claspill · Accepted solution]

Hello @Max 

The change will not work because when you put a series of IF conditions together like that the logic is "If all these conditions are true..." So your rule now says 

"If the trigger issue is a Subtask and the trigger issue is a Task..."

A single issue can't be two different types at the same time.

Instead of having two IF conditions have just one like this:

Using two edit actions won't work the way you want.

An Automation is triggered by a change on a single issue.

The branch you are using is For Parent. Whether the trigger issue is a Subtask or a Task the branch will shift focus to that issue's parent; the subtask's parent Task or the Task's parent Epic.

Using two Edit actions will try to perform those edits on the same, single parent issue of the trigger issue. The second Edit action on the same field will overwrite the first Edit action.

I would recommend you change the rule as follows.

Inside the branch for the first step add a Lookup Issues action to get a list of all the child issues of the Parent. Within the branch the {{issue}} smart value refers to the issue in focus by the branch - the Parent issue of the trigger issue.

{{lookupIssues}} is a list smart value that will reference the list of issues returned by the Lookup Issues action.

With a list of issue, you can use the sum function to total up the value of some specific numeric fields of the issues in that list. Story points is one such field where you can use sum. So then use this edit action to set the Story points field of the parent issue to the sum of the Story points of the child issues found by the Lookup Issues action.

Lastly, when the points on a subtask change that will trigger this rule to update its parent Task. That changes the points on the Task. In order to have that change trigger this rule again so that the Task's parent Epic is updated you need to check this box on the Rule Details page.

[Max]

@Trudy Claspill perfect explanation! thank you

[Tomislav Tobijas _Koios_]

Hi @Max ,

I would suggest taking a look at the following discussion: https://community.atlassian.com/t5/Automation-questions/Re-Re-Sum-up-Story-points-to-epic/qaq-p/2388810/comment-id/7110#M7110

UI maybe looks a bit different but the concept is the same. {{issue.subtasks}} is a specific and 'unique' smart value so you cannot just replace it with {{issue.tasks}} > that's why you're getting the error.

Anyway, once you find all child issues from the parent/Epic (with the Lookup issues action), you can use sum function when editing field on the parent.

Hope this helps.

Cheers,
Tom

[Trudy Claspill]

We recommended the same solution ;-)

I should've refreshed my screen before finally posting my response.

[Tomislav Tobijas _Koios_]

@Trudy Claspill I know the feeling 😄 No worries.

[Max]

update:

here is the context of the Story Point Field