Determine custom field ID properly, to use in automation rule "Additional fields"

[Boris Ahrendt]

Hi all,

We're trying to set an automation: when linked Jira work ticket status is updated --> edit custom field in Idea with the work ticket "FixVersions" data (along with updating Idea status).

The "FixVersions" is a multi-select field in Jira project, and the custom field I created is a short text format. I would expect then the trigger to pass on the version (e.g. 1.1.1) into the custom field.

Here's what we have, and it validates OK:

However, there is no update to the custom field when the trigger happens. I'm thinking that this might be due to the field ID. It shows like this in the JQL method:

I have tried using just the ID nr "10402" as well, but this silently fails as well.

Anyone with any tips on getting this to work? Thanks!

[Bill Sheboy]

Hi @Boris Ahrendt -- Welcome to the Atlassian Community!

First thing, for automation questions it is helpful to provide all of the context, with images of your complete rule and the audit log details...rather than just part of the rule.

For the moment, I am hypothesizing the rule trigger is not relevant for the symptom you see.

Next, please confirm you are trying to store the trigger work item's fix version names in the Short Text field.  If so, the JSON syntax you show is incorrect; please look here to learn more, and perhaps try this:

{
  "fields": {
    "customfield_10402": "{{triggerIssue.fixVersions.name}}"
  }
}

Finally, please note the Fix Versions field is a list of values.  Thus, if you have multiple versions associated to the trigger work item, they will appear in your custom field as a comma-separated values list of names.

Oops, I missed your primary question!  To identify the supported smart values and custom field ID values for automation rules, please use this how-to article:

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill