Consistent APIs for option fields

Across our documentation, there isn't a clear enough distinction between option and option2 in the API. For that matter, there it is rather confusing that each works differently in the REST API.

The admin docs just explain "Select list (single choice)". This leads to confusion when developers are trying to understand how to create JSON for a custom field, where the docs use the term "Single-select custom field". Developers have no way of knowing that is different from the kind of "Single-select custom field" that can be created via Atlassian Connect. I was unable to find any documentation on how to properly set the option2 custom field.

Although the doc gap might be considered a "bug", what I would really want is not to need more docs. It would be better if the option fields worked the same.

option works like this:

"customfield_11449" : { "value": "option3" }

or

"customfield_11449" : { "id": 10112 }

option2 works like this:

"customfield_11449" : 1