I updated a dropdown custom field via JIRA API using this payload:
{
"fields": { "custom_A": { "option": "Valid" } }
}
but retrieval returns a different value. Am I proceeding correctly?
I experienced similar issues when working with JIRA’s custom dropdown fields. From my experience, the payload you provided looked correct, but sometimes the API returns the normalized values rather than what you input. In one project I worked on, I discovered that the custom field was set up to accept additional metadata which was then processed by JIRA’s internal mapping before returning the value. Verifying whether the custom field configuration requires an ID or a more complex object worked out for me. I suggest reviewing the custom field schema in your settings to ensure that the data type and key formats match what is expected.
Based on my experience, it can be beneficial to verify the structure of your payload against the field schema defined in your JIRA instance. In one project I was involved in, similar issues arose because the API required not only the display value but also an associated identifier for the dropdown option. Confirming that the exact format expected by the field settings is maintained typically resolves discrepancies between submitted data and retrieved values. Revisiting the documentation for custom field types may help clarify any additional parameters needed.