Hello! We imported several thousands tickets (using JSON importer) and would like to be able to find them by their old IDs. During import these were specified as {{externalId}}. For example:
{ "externalId": "HLR219", "issueType": "Defect", ...
However, when I attempt to search (using JQL):
curl -D- -X GET -H 'Content-Type: application/json' ......./jira/rest/api/2/search\?jql=externalId=HLR219
I get an error:
{"errorMessages":["Field 'externalId' does not exist or you do not have permission to view it."],"errors":{}}
The tickets are all showing their original IDs -- the custom field is named "External issue ID" and was populated by the JSON-importer during import...
If I dump the entire issue, I see these label (such as HLR219) as values of customfield_10801 of each ticket. However, searching for such custom field does not work:
{"errorMessages":["Field 'customfield_10801' does not exist or you do not have permission to view it."],"errors":{}}
In JQL you have to use either the name of the customfield, so this should be "External issue ID", or the ID like this "cf[10801]".
And I guess you would need to use the "~" operator instead of "="
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Although, it would seem, going directly to the database is both faster and easier -- one does not even need to know the numeric ID of the custom field in advance -- only its value. For example:
select jiraissue.id as id, pkey, assignee, stringvalue from jiraissue join customfieldvalue on jiraissue.id=issue where stringvalue='HLR219'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.