Are there alternative syntaxes to {{issue.customfield_[custom field numeric Id}}}?

[Phil Bustin]

I successfully used {{issue.customfield_20232}} in an automation.  What alternatives if any would also work?

{{issue.Development Manager.20232}} was unsuccessful, for example.

[Trudy Claspill · Accepted solution]

Hello @Phil Bustin 

What problem are you trying to solve?

To access a custom field with a smart value in automation you can use either the customfield_##### nomenclature or you can use the field name; i.e. Development Manager. You don't need to combine the field name and the numeric ID.

[Phil Bustin]

Just trying to remember how I used the field name correctly as a smart value before, since that's easier than looking at my list of custom fields and their numeric Id's, or selecting the field in Settings > Issues > Custom fields to find the numeric Id in the URL.  (I should have examined my existing automations to find the answer, rather than posting a question.)

I also thought there might be more than one way to reference the name itself as a smart value, and I guess there is--either the name itself or preceded by "issue."

[Bill Sheboy]

Hi @Phil Bustin 

You noted this:

I also thought there might be more than one way to reference the name itself as a smart value, and I guess there is--either the name itself or preceded by "issue."

Context within a rule is important when referencing smart values, and so sometimes omitting the issue prefix can cause an unexpected result.  For example, in this sample rule:

• trigger: manual...  At this point, {{issue.someField}}, {{triggerIssue.someField}}, and {{someField}} refer to the same thing.
• branch: some branch... At this point, {{issue.someField}}, {{triggerIssue.someField}}, and {{someField}} refer to the same thing.
  • action: another action... At this point, {{issue.someField}} and {{someField}} refer to the current issue in the branch, but {{triggerIssue.someField}} refers to the trigger issue.
• action: one more action... At this point, {{issue.someField}}, {{triggerIssue.someField}}, and {{someField}} again refer to the same thing.
• action: lookup issues with some JQL
• action: one more action using {{#lookupIssues}}{{someField}}{{/}}... At this point, {{someField}} refers to an issue from the lookup, and {{issue.someField}} or {{triggerIssue.someField}} would be undefined (i.e., null) if referenced inside the iterator.

Kind regards,
Bill

[Phil Bustin]

Thanks.  I've stored this in my Development Notes document.

[Kian Stack Mumo Systems · Accepted solution]

Try {{issue.Development Manager}}