Issue with Zammad filtering: Unable to Filter on objects by external data source fields

Infos:

  • Installation method: Kubernetes Helm Chart
  • Operating system rhel 9.4
  • Database + version: postgressql 15.4.0
  • Elasticsearch version: 8.12
  • Browser + version: chrome 127.0.6533.73, Firefox 128.0.3

Actual behavior:

  • When creating a report profile, a trigger or a workflow in Zammad and attempting to filter tickets based on fields that utilize an external data source, the system fails to perform the search. Specifically:

  • No results are returned when filtering by these fields. The loading icon just keeps spinning:
    364702191-dc610c79-bc0f-408d-8f76-295c3c2d53d2

  • In “Expert Mode,” an error message appears: “no implicit conversion of Symbol into Integer”.

  • In the browser console, the following error occurs whenever typing in the field: Uncaught TypeError: Cannot read properties of undefined (reading 'params')

  • The server log contains the following error: ERROR -- : Selector::Sql.get->InvalidCondition: Invalid condition pre_condition nil {:name=>"ticket.afdeling", :operator=>"is", :value_completion=>"test", :value=>[]}!.

Expected behavior:

  • When filtering tickets (or other objects) based on fields that utilize an external data source:

  • The system should correctly return tickets matching the filter criteria.

  • No errors should be triggered in the browser console, server logs, or in the interface.

Steps to reproduce the behavior:

  1. Go to Zammad’s Objects section and create a custom ticket attribute using an external data source.
  2. Create or update a ticket, filling in the custom attribute field that utilizes the external data source.
  3. Go to the Reports section and create a new report profile.
  4. Attempt to filter tickets based on the custom attribute field created in step 1.
  5. Notice that no results are returned, and errors occur in “Expert Mode” and the browser console.

I see you also created a GitHub issue. Can you please decide for one place to post? You’re potentially keeping people busy twice. That’s unfair for others. I believe you have received your answers in the issue already.

Sorry, there was no activity on the issue when created this thread. I will take notice.