Report Profile crashes

Infos:

  • Used Zammad version: 3.3.X
  • Used Zammad installation source:
  • Operating system: Windows 10
  • Browser + version: Chrome

Expected behavior:

  • A report was created to display all tickets in different statuses without agents.
    It works in the preview.

Actual behavior:

  • An error message appears

{“error”:“Unable to process GET request to elasticsearch URL ‘http://localhost:9200/zammad_production/Ticket/_search’. Check the response and payload for detailed information: \n\nResponse:\n#\u003cUserAgent::Result:0x00005617938db5e8 @success=false, @body=”{\“error\”:{\“root_cause\”:[{\“type\”:\“query_shard_exception\”,\“reason\”:\“failed to create query: {\\n \\\“bool\\\” : {\\n \\\“must\\\” : [\\n {\\n \\\“terms\\\” : {\\n \\\“state_id\\\” : [\\n \\\“8\\\”,\\n \\\“1\\\”,\\n \\\“2\\\”,\\n \\\“3\\\”\\n ],\\n \\\“boost\\\” : 1.0\\n }\\n },\\n {\\n \\\“term\\\” : {\\n \\\“owner_id\\\” : {\\n \\\“value\\\” : \\\”\\\",\\n \\\“boost\\\” : 1.0\\n }\\n }\\n },\\n {\\n \\\“range\\\” : {\\n \\\“created_at\\\” : {\\n \\\“from\\\” : \\\“2019-12-31T23:00:00Z\\\”,\\n \\\“to\\\” : \\\“2020-12-31T22:59:59Z\\\”,\\n \\\“include_lower\\\” : true,\\n \\\“include_upper\\\” : true,\\n \\\“boost\\\” : 1.0\\n }\\n }\\n }\\n ],\\n \\\“must_not\\\” : [\\n {\\n \\\“term\\\” : {\\n \\\“state.keyword\\\” : {\\n \\\“value\\\” : \\\“merged\\\”,\\n \\\“boost\\\” : 1.0\\n }\\n }\\n }\\n ],\\n \\\“disable_coord\\\” : false,\\n \\\“adjust_pure_negative\\\” : true,\\n \\\“boost\\\” : 1.0\\n }\\n}\",\“index_uuid\”:\“br2zfHAlT_yr6Tzd6sJTow\”,\“index\”:\“zammad_production\”}],\“type\”:\“search_phase_execution_exception\”,\“reason\”:\“all shards failed\”,\“phase\”:\“query\”,\“grouped\”:true,\“failed_shards\”:[{\“shard\”:0,\“index\”:\“zammad_production\”,\“node\”:\“5A25Wd3kS32cobkBHA5N3g\”,\“reason\”:{\“type\”:\“query_shard_exception\”,\“reason\”:\“failed to create query: {\\n \\\“bool\\\” : {\\n \\\“must\\\” : [\\n {\\n \\\“terms\\\” : {\\n \\\“state_id\\\” : [\\n \\\“8\\\”,\\n \\\“1\\\”,\\n \\\“2\\\”,\\n \\\“3\\\”\\n ],\\n \\\“boost\\\” : 1.0\\n }\\n },\\n {\\n \\\“term\\\” : {\\n \\\“owner_id\\\” : {\\n \\\“value\\\” : \\\”\\\",\\n \\\“boost\\\” : 1.0\\n }\\n }\\n },\\n {\\n \\\“range\\\” : {\\n \\\“created_at\\\” : {\\n \\\“from\\\” : \\\“2019-12-31T23:00:00Z\\\”,\\n \\\“to\\\” : \\\“2020-12-31T22:59:59Z\\\”,\\n \\\“include_lower\\\” : true,\\n \\\“include_upper\\\” : true,\\n \\\“boost\\\” : 1.0\\n }\\n }\\n }\\n ],\\n \\\“must_not\\\” : [\\n {\\n \\\“term\\\” : {\\n \\\“state.keyword\\\” : {\\n \\\“value\\\” : \\\“merged\\\”,\\n \\\“boost\\\” : 1.0\\n }\\n }\\n }\\n ],\\n \\\“disable_coord\\\” : false,\\n \\\“adjust_pure_negative\\\” : true,\\n \\\“boost\\\” : 1.0\\n }\\n}\",\“index_uuid\”:\“br2zfHAlT_yr6Tzd6sJTow\”,\“index\”:\“zammad_production\”,\“caused_by\”:{\“type\”:\“number_format_exception\”,\“reason\”:\“empty String\”}}}]},\“status\”:400}", @data=nil, @code=“400”, @content_type=nil, @error=“Client Error: #\u003cNet::HTTPBadRequest 400 Bad Request readbody=true\u003e!”\u003e\n\nPayload:\n{:query=\u003e{:bool=\u003e{:must=\u003e[{“terms”=\u003e{“state_id”=\u003e[“8”, “1”, “2”, “3”]}}, {“term”=\u003e{“owner_id”=\u003e""}}, {:range=\u003e{“created_at”=\u003e{:from=\u003e"2019-12-31T23:00:00Z", :to=\u003e"2020-12-31T22:59:59Z"}}}], :must_not=\u003e[{“term”=\u003e{“state.keyword”=\u003e"merged"}}]}}, :size=\u003e0, :aggs=\u003e{:time_buckets=\u003e{:date_histogram=\u003e{:field=\u003e"created_at", :interval=\u003e"month", :time_zone=\u003e"Europe/Berlin"}}}, “sort”=\u003e[{:updated_at=\u003e{:order=\u003e"desc"}}, “_score”]}\n\nPayload size: 0M"}

Steps to reproduce the behavior:

  • This is the filter:
    image

Sounds like exactly this bug:

Ay, is it. Do you know, when it will be fixed?

As my crystall ball is broken - no.
Sorry, but we can’t provide ETAs on developments and bug fixing in general.

Sure, I can understand that.
But can you say if it could be fixed in the next version?
Or where is it from the Prio? Can it be prioritized by payment?

As neither Milestone nor Project are filled in, this proberbly won’t happen.

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