Issue

When accessing some custom fields from the Element Connects add-on (nFeed) using the following smart value, the Automation rule uses the key-value but not the display value:

{{issue.fields.customfield_12800}}

The reason why the key-value is returns instead of the display value, is because Automation for Jira pulls the value of custom fields using the following Jira API call, and this Jira API calls returns the key-value of Elements Connect's custom fields:

<JIRA_BASE_URL>/rest/api/2/issue/<ISSUE_KEY>

To get the actual display value from this field, Automation for Jira would need to access the Elements Connect API to get the display value.

Suggestion

Improve the way Automation for Jira gets the value of Elements Custom fields by accesing the add-on API.