You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installation method: any
Operating system (if you're unsure: cat /etc/os-release ): any
Database + version: any
Elasticsearch version: any
Browser + version: MS Edge v.120.0.2210.121 (64-Bit)
Actual behaviour
If I select an attribute with type "External data source field" in a trigger as an action, then it finds nothing here and searches for an eternity.
When using "external data source" in the action for a trigger, i can also search for entries in the "external data source" and get results as a dropdown menu like in the ticket itself to select the wanted entry.
Steps to reproduce the beha1viour
Create a custom field with an external data source type.
Open new Trigger (or Macro, Scheduler...) form
Select that custom field as a an action
Enter a term to search for.
Search is stuck, results are never returned and animation plays forever
Support Ticket
Ticket#10154217
I'm sure this is a bug and no feature request or a general question.
yes
The text was updated successfully, but these errors were encountered:
mantas
changed the title
Using external data source object as a trigger execute the search going on into infinity and delivers no results
External data source search gets stuck when it is added as a condition or an action
May 31, 2024
Used Zammad Version
6.3.0-1713882094.d1107375.bullseye
Environment
Actual behaviour
If I select an attribute with type "External data source field" in a trigger as an action, then it finds nothing here and searches for an eternity.
Object:
Trigger:
Similar to this Issue:
#5006
Expected behaviour
When using "external data source" in the action for a trigger, i can also search for entries in the "external data source" and get results as a dropdown menu like in the ticket itself to select the wanted entry.
Steps to reproduce the beha1viour
Support Ticket
Ticket#10154217
I'm sure this is a bug and no feature request or a general question.
yes
The text was updated successfully, but these errors were encountered: