Issue Summary

• When referring to custom fields by their names within automation rules, the rule tries to access it by its translated field name

Steps to Reproduce

1. Create a custom field and name it "Testing"
2. Create an automation rule which adds a comment to an issue and refer to that field by using its name: {{issue.testing}}
3. Put some text into the field.
4. When the automation executes, it adds the field's content to the issue as a new comment.
5. Add a translation for "Spanish" like "Pruebas" to the field.
6. Execute the automation again, it will add an empty comment.
7. Change the rule actor's language to Spanish.
8. Update the rule to include the translated name "{{issue.Pruebas}}".
9. When the rule gets executed again, it will add the field's content again.

Expected Results

• The automation rule should consider the original name of the custom fields in the automation rules instead of the translated name.
• Therefore, even if we add a translation of the custom field "Testing" as "Pruebas", it should always consider Testing as the field name irrespective of the rule actor's language settings.

Actual Results

• As per Accessing issue fields, field names are not case-sensitive and are translated using the rule actor's language setting.
• Therefore, even if the Jira user's language setting is set to "English" and the automation rule actor's language setting is set to "Spanish", it considers the translated name "Pruebas" as the field name instead of the original name "Testing".

Workaround

The workaround is to use custom field id in the automation rule instead of the custom field name.