Discrepancy between field names in HTTP GET fields and jql param

[Jorge Zapata]

I'm having the following field as returned by the 'fields' HTTP GET:

{
 "id": "customfield_10500",
 "key": "customfield_10500",
 "name": "Reviewer",
 "custom": true,
 "orderable": true,
 "navigable": true,
 "searchable": true,
 "clauseNames": [
   "cf[10500]",
   "Reviewer"
   ],
 "schema": {
   "type": "user",
   "custom": "com.atlassian.jira.plugin.system.customfieldtypes:userpicker",
   "customId": 10500
 }
}

If I do a 'search' HTTP GET using fields=reviewer I do not get the corresponding field on the answer. If I use the fields=customfield_10500 it does work

If I do a JQL like 'Reviewer = Foo' the search is done correctly. Any other value gives me JQL error string: 

["Field 'customfield_10500' does not exist or you do not have permission to view it."]

As you can see there's no way to specify the same field name on the 'jql' or the 'fields' params which leads to problems when introspecting the service and performing searches automatically.