Why am I getting different JSON structure for different custom field values

[Brad Hayes]

I have a custom field which is a checkbox.  This also happens for a selection field that has options of None and Yes.

If it is unchecked, in the REST API for the Issue I get

 "customfield_11025": null,

If it is checked I get

 "customfield_11025": [
{
  "self": "https://dmsidmsi.atlassian.net/rest/api/2/customFieldOption/10504",
  "value": "Canceled",
  "id": "10504"
}
],

 This makes it impossible to define a structure to capture the JSON into.  Regardless of which way I code it, when I encounter the opposite my progam panics because it doesn't match the defined structure.

[Michael Raj]

Hi @Brad Hayes ,

add "if" and check if value is null. Now you can build structure for both options.

Best,

Michael

[Brad Hayes]

Thanks Michael.  I was able to make it work doing that, but I was also curious why I was getting different values for different fields that according the administrator were both boolean values.  Seems there's multiple ways to define fields and they produce different results.

brad