What is the difference between the field3-value and field3-value-id properties when updating ticket XML? I have tried setting values for either and I seem to be getting values mixed up or somehow cross-referencing them with other tickets. I can also call api/v1/projects/{0}/custom_field_values.xml and get something like 3000 records. I hope I don’t have to pull these down just to check the values of my tickets? Because it seems like my ticket has the id but not the actual VALUE which I want.

Actually, I guess all I’m asking is could somebody post an example of how to update the custom field value of a ticket? Thanks.

Ben,

As you have probably noticed, the custom fields can be one of two different dispositions, “text” or “list”. The list disposition would require you to specify fieldX-value-id since you are choosing an ID from a set list of options.

The text disposition, however, does not use a restricted list of values, but rather, allows you to specify an arbitrary value. This means you can use the fieldX-value property to either create a new value or associate the ticket with an already existing value in fieldX simply based on the text of the “value” property.

For more information, please see the Ticket data model in the Unfuddle API documentation.