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 show success but the value showing is NONE

Alon Shoham_w1572v

Hi everyone,

I've created an automation that takes a number value (from a custom field) in a sub-task and adds it to a field (also a numeric field) in the parent Story.

The automation shows 'Success' but the actual value in the story is None (instead of the numeric value from the trigger subtask).

I'd love to get some help here..thanks!

Screenshot 2022-10-25 124616.png

Accepted answers

Bill Sheboy

Hi @Alon Shoham

You are trying to copy the value from the trigger issue (subtask) to the parent issue, correct?

If so, you need to reference the trigger issue with:

{{triggerIssue.customfield_11028}}

If instead you are trying to sum the value for all children subtasks, rather than copy one, that would require a different value, using the parent to gather the subtask values:

{{issue.subtasks.customfield_11028.sum}}

Kind regards,
Bill

All comments

Aron Gombas _Midori_

You can easily troubleshoot the automation rule execution if you place "Log" actions (multiple!) between the actual action. You can use those to print smart values to your log. Then you check the log messages of your last execution.

It should help to find the root cause here.

Bill Sheboy

Hi @Alon Shoham

You are trying to copy the value from the trigger issue (subtask) to the parent issue, correct?

If so, you need to reference the trigger issue with:

{{triggerIssue.customfield_11028}}

If instead you are trying to sum the value for all children subtasks, rather than copy one, that would require a different value, using the parent to gather the subtask values:

{{issue.subtasks.customfield_11028.sum}}

Kind regards,
Bill

Alon Shoham_w1572v

Wow Bill it's working !! Thank you so much!

Such a tiny detail that took me hours to work on!

Thank again!

Alon Shoham_w1572v

Thanks! If I understand correctly there is a way to see the specific reason for the failure?
Where should I put "log"?

Aron Gombas _Midori_

See item 1 and 2 in this page: https://support.atlassian.com/cloud-automation/docs/debug-an-automation-rule/

Bill Sheboy

I am glad to learn that it is working now!

This is a common symptom for rule writing, and something to remember is the meaning of {{issue}} depends on where you are in a rule...For example:

trigger: some trigger At this point, both {{issue}} and {{triggerIssue}} refer to the issue(s) which started the rule.
action: some action No change in meaning yet.
branch: some branch to issues No change in meaning yet.
- action: another action Inside of a branch...{{issue}} refers to the issue(s) branched-to and {{triggerIssue}} refers to the issue(s) which started the rule.
action: some other action Again outside of the branch, both {{issue}} and {{triggerIssue}} refer to the issue(s) which started the rule.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud