automation add filed value

Hi All

We have been trying to use automaion add field value to comment recently.

At first, "{{issue.filedname}}" could be displayed normally. However, after we translated this custom field, using the following methods failed to obtain the corresponding value:

I attempted to use the {issue+field name} format, but I couldn't retrieve the corresponding value, no matter which environment's field name I used.

4 answers

1 accepted

0 votes

Answer accepted

We have finally decided to unify the field names and no longer perform translation.

Thanks everyone help

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Hi @arno

For a question like this, context is important for the community to help. Please post the following:

what version of Jira are you using: Cloud, Server, or Data Center
an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the audit log details showing the rule execution
explain what is not working as expected and why you believe that to be the case

Until we see those...

Smart values are name, spacing, and case-sensitive...and frequently do not match the field's displayed name on the Jira pages. When an incorrect smart value is used, that returns a null value.

To learn the smart value (or custom field ID), field structure, and if it is supported by automation rules, please use this how-to article:

https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html

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.

Comment

Hi @Bill Sheboy

thank you for your reply

we are use jira server, server version :8.13.3

our automation like this:

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks for that information, and...

Please post an image of the audit log details showing the rule execution. That will confirm which rule steps processed and if there were any errors.

Did you try the how-to article to confirm your smart values / custom field ID's are correct?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

hi @Bill Sheboy

sorry,the log did not show any errors. As I mentioned, when I did not translate this field, I was able to obtain the corresponding value using any method.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Did you try the how-to article to confirm your smart values / custom field ID's are correct?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi @Bill Sheboy

Yes, the field ID is correct.

I once again referred to the official documentation and discovered this explanation

If you're trying to access custom fields with translated names in your smart values, then use the language set for your rule actor user.

I'm not quite sure. Do I need to add multiple rules to ensure that users obtain the correct field values in different language environments? just like this:

BUG ID：

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

This appears to be a known defect which was fixed in a later release than you are using: 10.2.1

https://jira.atlassian.com/browse/JIRAAUTOSERVER-1025

https://confluence.atlassian.com/jirasoftware/issues-resolved-in-10-2-1-1456346546.html

If you do not upgrade versions, you could try the workarounds noted in the defect, although I suspect they may not work to maintain the translated values.