Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation show success but the value showing is NONE

Alon Shoham
Contributor
October 25, 2022

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 

2 answers

1 accepted

1 vote
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 25, 2022

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
Contributor
October 26, 2022

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

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

Thank again!

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 26, 2022

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.
Like # people like this
1 vote
Aron Gombas _Midori_
Community Champion
October 25, 2022

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.

Alon Shoham
Contributor
October 26, 2022

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_
Community Champion
October 26, 2022
Like Alon Shoham likes this

Suggest an answer

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

Atlassian Community Events