I have the following expression for Edit issue field:
{{#=}{{issue.Impact.value}} * {{issue.Effort.value}}{{/}}
In the audit log, it says SUCCESS
but the field remains empty
Atlassian support replied and fixed my expression.
Now it works:
{{#=}}{{issue."Impact"|0}} * {{issue."Effort"|0}} {{/}}
What are the types of those fields?
If they are numbers, you may used them directly with either of these methods:
{{#=}{{issue.Impact}} * {{issue.Effort}}{{/}}
{{issue.Impact.multiply(issue.Effort)}}
The .value is only needed if the fields are selection fields.
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting update.
I experimented and set the default value of Prioritization calculated field (the one that needs to be updated) to 0.
Once I ran the rule, it changed from 0 to empty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you please add to you automation rule the action "log action" and add inside it {{#=}{{issue.Impact.value}} * {{issue.Effort.value}}{{/}} then try to run it and let me know what does it show in the logs of the rule.
also can you please share the type of the three below field:
- the filed you are trying to add to the result of {{#=}{{issue.Impact.value}} * {{issue.Effort.value}}{{/}}
- Impact
- Effort
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thank you @Yulia Zhyliaieva for sharing the above.
since the two fields that you are multiplying are custom fields, you need to do the following:
setting from top right corner
issues
custom fields
search for each of the two fields and click edit details
new page will open
in the browser URL, you will find a 5 digit code..replace each of the fields in your rule like the following ex: instead of {{issue.Impact.value}} use {{issue.customfield_xxxxx(code from previous step}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I already did that. The rule runs the same.
There is an interesting update on this case (above):
I experimented and set the default value of Prioritization calculated field (the one that needs to be updated) to 0.
Once I ran the rule, it changed from 0 to empty
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
apologies @Yulia Zhyliaieva can you please try {{issue.customfield_xxxxx.value}} and let me know
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is how the expression looks now, and yet the desired calculated field is empty: {{#=}{{issue.customfield_11896.value}} * {{issue.customfield_11897.value}}{{/}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another update - when I try to include different other fields into the automation rule, the placeholder is set to different values.
However, for my specific field it says that the field will be cleared.
Seems like whatever expression I fill in there, it does not matter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Allow me please to clarify few things first, having the 0 added by default to "Prioritization calculated" field then it becomes empty after running the rule, is expected behaviour since your equation outcome is null (as you can see from the automation rule log) and this null is replacing the 0
second, the placeholder message that you are seeing for this field "This field will be cleared" means that: whatever you will enter in this box will clear that field existing value and replace it with what you will enter
last, i understand that this process might take a bit but in order to get to know the reason we would need to do some troubleshooting....can you please add to the automation rule few log actions and add to one of them {{issue.customfield_11897.value}} and to the other {{issue.customfield_11897}} and please make sure that this field has value.
also it would be great if you can share a screenshot for your entire automation rule so i can better understand the logic of it and from where it is triggered and how the values are being passed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.