Title: Core Workflow - Allow Auto Select for External Data Source field
-
What is your original issue/pain point you want to solve?
When there is only one value returned for the search, it would be nice if we could set it automatically (in order to get external data visible into Zammad). If there is indeed an option to put the value of a data source dropdown to the first value of the search result through the API, that would also work for me. -
Which are one or two concrete situations where this problem hurts the most?
If you have another data source field with only one result value, for example to show the status of a linked jira issue (ticket.jira_issue_key), it would help to make data readily available just by searching one field -
Why is it not solvable with the Zammad standard?
Currently, the option auto select only exists for fixed dropdowns, but is not available on the data source field. I would also be able to work with #{jira.issue_status.0} for example, but I could not get this to work. -
What is your expectation/what do you want to achieve?
I would like to make easily maintainable trigger that update fields querying external data sources when there is only one distinct search result (i.e. the info I’m looking to display).
Your Zammad environment:
- Average concurrent agent count: 2
- Average tickets a day: roughly 120 in Freshdesk, we’re currently testing Zammad for a smaller Team
- What roles/people are involved: our technical support team and the security team, handling CVE inquiries
Anything else which you think is useful to understand your use case:
Ideally, and that would be cherry on the cake, there would be a mapping section in the external field creation dialog that allows you to set existing ticket fields to values from the search result.I created a quick mockup for the field mapping, just to clarify what I mean:
The mapped ticket field column should perhaps be a dropdown of ticket fields, but you get the idea 
Thanks for reading, I hope its somewhat comprehensive
Best,
Stephan