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

Can Automation for JIRA calculate a field on a linked issue using math functions as action?

unknown

I am currently working on the challenge to implement project controlling in JIRA and was wondering whether a field on an issue called project could automatically be calculated when a value on a linked sub-project issue changes?

I have a hierarchy over four levels using sub-tasks already so changing the link between project and sub-project to a task-sub-task-relationship is not an option.

Accepted answers

andreas_qezsu8

Hi Nadine,

I'm not 100% sure I fully understand your exact setup, but with Automation for JIRA, you can action related issues that you find based on JQL. Match functions can be applied to those.

So for example you could have a rule like this:

Trigger: Field value changed with your field selected
JQL condition: type = sub-task ?
Branch rule with Parent
- Edit issue action where you set the 'project' field to something like:
```
{{#=}}{{triggerIssue.someField}} + 25{{/}}
```

'triggerIssue' would refer to the issue produced by the trigger in this example. 'someField' is the name of your field.

Not sure if this helps. Like I said I need more details about your exact case. Bacially in the branch rule, you could also use JQL to find the related issue somehow.

Cheers,

Andreas

All comments

andreas_qezsu8

Hi Nadine,

I'm not 100% sure I fully understand your exact setup, but with Automation for JIRA, you can action related issues that you find based on JQL. Match functions can be applied to those.

So for example you could have a rule like this:

Trigger: Field value changed with your field selected
JQL condition: type = sub-task ?
Branch rule with Parent
- Edit issue action where you set the 'project' field to something like:
```
{{#=}}{{triggerIssue.someField}} + 25{{/}}
```

'triggerIssue' would refer to the issue produced by the trigger in this example. 'someField' is the name of your field.

Not sure if this helps. Like I said I need more details about your exact case. Bacially in the branch rule, you could also use JQL to find the related issue somehow.

Cheers,

Andreas

unknown

Hello Andreas

Thanks a lot for your prompt reply.

Actually, I'm not sure I fully understand my setup... ;-) but let me try to explain:

I have a standard issue type project linked to 1-n other standard issue types sub-project via the link has sub-project. Both issue types have a numeric field called Labour Hours and what I need to achieve is the Labour Hours for issue project being automatically updated as sum of Labours Hours of all linked sub-projects when Labour Hours of one sub-project is updated.

I have already configured a prototype using tranistion triggers and post-functions for calculations which works fine. But now my customers wants values to be updated not using transitions. We could use Script Runner or a custom add-on to achieve this but I prefer a solution not requring to much scripting which is also maintained as a marketplace add-on. Hence, I would love to use Automation for JIRA.

andreas_qezsu8

Hi Nadine,

Ah right so you want to calculate the aggregate sum of various linked issues. We don't support this yet, but we're already tracking this request at https://codebarrel.atlassian.net/browse/AUT-476.

We've got quite a few higher priority items in our backlog at the moment so it will be a while before we can get to this, but we'll let you know when we get a chance to work on this.

Cheers,

Andreas

Étienne Borella

We have the same scenario that we'd like to address.

Our hierarchy of issues is made of Epics / Stories / Subtasks.

We'd like to have a "Rolled Up Time Spent" custom field that sums up the time spent on a issue with the total time spent on related issues below when time is logged against either the task itself or its related issues.

e.g. when time is logged on a subtask (or the subtask is edited), "Rolled Up Time Spent" is updated at the parent Issue & the Epic levels (may be a cascade of 2 automations here, due to the 3 levels hierarchy).

I don't seem to be able to login and vote for AUT-476, so I add this comment here to say that I am interested ;-)

Thanks

Piotr Zolnierek

mustafa korkmaz

Patrick Haley

This is for people who find this in the future. I was able to set up a Jira Automation to calculate a value.

Trigger: Montior field values for changes.

Then I created Variables using Smart Values for each of the custom fields I created.

Once I had all of the variables defined, the final automation component was an Edit Issue field. I had set up a custom view only field so that it couldn't be edited directly by users. I used Andreas formula in the accepted comment which worked perfect for me.

{{#=}}({{Reach}} * {{Impact}} * {{Confidence}}) / {{Effort}}{{/}}

Steve Letch_j0fncr

Very nice, I really wish they'd port over all these nice functions to the server/data center versions

mahi kamal

hi , can i use automation and make formula with custom field? if i can..could you please help me?

Patrick Haley

Yes it’s possible. See my previous reply in this thread for more info.

mahi kamal

thank you for explain..but i have problem could you please help me? sx 1_23_2023 10_05_52 AM.png

Patrick Haley

I think it's because you're using an If/Else statement, but it doesn't contain an action when the first If matches.

You're basically saying:

IF custom_field_11225 is not empty

THEN do nothing <-- This is what is causing the issue

IF custom_field_11226 is not empty

THEN edit issue fields

If the first IF statement does not have an action and all you're doing is checking if that field isn't empty before the next IF statement, consider using an Issue fields condition instead.