Could not parse jira response unexpected field – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch tries to parse a response from Jira and encounters an unexpected field. This could be due to changes in the Jira API or a mismatch between the expected and actual data structure. To resolve this issue, you can 1) Check the Jira API documentation for any changes and update your Elasticsearch queries accordingly. 2) Review the data structure of the Jira response and adjust your parsing logic to handle the unexpected field. 3) If the unexpected field is not needed, you can configure Elasticsearch to ignore it during parsing.

This guide will help you check for common problems that cause the log ” could not parse jira response. unexpected field [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: response, plugin.

Log Context

Log “could not parse jira response. unexpected field [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (Field.ERROR_MESSAGES.match(currentFieldName; parser.getDeprecationHandler())) {
 while ((token = parser.nextToken()) != XContentParser.Token.END_ARRAY) {
 } else {
 throw new ElasticsearchParseException("could not parse jira response. unexpected field [{}]"; currentFieldName);
 } catch (Exception e) {
 errors.add("Exception when parsing jira response [" + String.valueOf(e) + "]");


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?