Get error when press Reporting button: [bool] failed to parse field[must]


  • Used Zammad version: 5.3.1-1675161621.b4b723eb.centos7
  • Used Zammad installation type: package
  • Operating system: Centos 7 3.10.0-1160.81.1.el7.x86_64
  • Browser + version: Microsoft Edge 109.0.1518.61

Expected behavior:

Zammad shows report

Actual behavior:

Zammad shows error:

Unable to process GET request to elasticsearch URL 'http://localhost:9200/zammad_production_ticket/_search'. Check the response and payload for detailed information:

#<UserAgent::Result:0x0000563a9114b050 @success=false, @body="{\"error\":{\"root_cause\":[{\"type\":\"x_content_parse_exception\",\"reason\":\"[1:51] [bool] failed to parse field [must]\"}],\"type\":\"x_content_parse_exception\",\"reason\":\"[1:51] [bool] failed to parse field [must]\",\"caused_by\":{\"type\":\"illegal_argument_exception\",\"reason\":\"field name is null or empty\"}},\"status\":400}", @data=nil, @code="400", @content_type=nil, @error="Client Error: #<Net::HTTPBadRequest 400 Bad Request readbody=true>!", @header={"x-elastic-product"=>"Elasticsearch", "content-type"=>"application/json; charset=UTF-8", "content-length"=>"182"}>


Payload size: 0M

Steps to reproduce the behavior:

  • Open Zammad page
  • click on “Reporting” button

Your reporting profile - all - most likely has been updated by anyone at some point.
By default this clause contains an empty state clause which technically is troublesome.

So the issue is fixed as soon as you correct the profile in the backend to something meaningful.

The documentation might help you on that journey:

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.