Unable to capture value in the Service Field in JIRA Automation

[mike_atrache]

I am trying to capture the value of a Field Type Service Field in my Jira Automation but the value is coming up blank when using the Log action component.  Affected Services: {{issue.customfield_11393}}

[mike_atrache · Accepted solution]

The root cause was a race condition inherent to JSM Portal submissions; the 'Affected Services' field wasn't fully populated when the automation triggered. Implementing a 10-second delay followed by a 'Re-fetch issue data' action successfully allowed the field values to settle, resolving the lookup failure.

[Bill Sheboy]

Hi @mike_atrache 

I recall when I tried this several years ago, none of the smart values in the help documentation worked...and there is no reference in the public REST API endpoints to get it either.  This seems to be one of the read-just-in-time smart values, limiting how it can be referenced.

I did try using the newer { } built-in lookup for a smart value and it does return a value.  Perhaps try that:

• create a test rule
  • scoped to your JSM project / space
  • with a Scheduled trigger and JQL to read a JSM work item by key
• add a Log action
• at the right side of the Log Message field, select the { } to View available smart values 
• type in the name for Affected Services 
• when it displays the field's custom field ID, select to copy the expression
• paste that in the Log Message
• test your rule

For example in my space, it was this:

{{issue.customfield_10057}}

Kind regards,
Bill

[mike_atrache]

The root cause was a race condition inherent to JSM Portal submissions; the 'Affected Services' field wasn't fully populated when the automation triggered. Implementing a 10-second delay followed by a 'Re-fetch issue data' action successfully allowed the field values to settle, resolving the lookup failure.

[Himanshu Tiwary]

Hi @mike_atrache ,

Try logging one of these instead

{{issue.customfield_12452.name}}

{{issue.customfield_12452.displayName}}

{{issue.customfield_12452.value}}

If the field allows multiple services, use {{issue.customfield_12452.name.join(", ")}}

A good way to troubleshoot is to first log the whole issue as JSON and inspect how that field is stored {{issue}} or {{issue.fields}}

[mike_atrache]

hey Himanshu, to see everything I tried {{issue.asJson}} but it came up empty as well. 

[Himanshu Tiwary]

Hi @mike_atrache ,

use the field’s dedicated smart value instead. For Affected Services, try

{{issue.affectedServices}}

{{#issue.affectedServices}}{{name}}{{/}}

Reference link Referance Link2 

[mike_atrache]

The root cause was a race condition inherent to JSM Portal submissions; the 'Affected Services' field wasn't fully populated when the automation triggered. Implementing a 10-second delay followed by a 'Re-fetch issue data' action successfully allowed the field values to settle, resolving the lookup failure.