Used Zammad version: 5.2
Used Zammad installation type: source
Operating system: Linux / Windows
Browser + version: Edge/ firefox (newest)
When new tickets arrived via mail, all tickets are assigned to the admin user?
we dont not know why this happens, for our workflow it would be better that all new ticket where unassigned.
Here is the history of an example
updated Ticket Last contact ‘10/10/2022 12:57’
updated Ticket Last contact (customer) ‘10/10/2022 12:57’
updated Ticket Escalation at (First Response Time) ‘10/10/2022 14:57’
updated Ticket Escalation at ‘10/10/2022 14:57’
email sent to ‘XXX’
notification Ticket ‘X(create:online)’
notification Ticket ‘y(create:online,email)’
notification Ticket ‘z(create:online)’
notification Ticket ‘zz(create:online)’
What is the reason for new tickets being assigned to the admin user?
October 12, 2022, 1:38pm
This part is not normal. Why is your ticket escalated at creation? You might want to check your SLA settings or your triggers for this escalation
I have checked SLA and disable everything for testing, but the AdminUser remains the creator of the ticket, see history below
How is the ticket being created? By mail? With what meta data?
Does the “admin user” actually exist?
The ticket was created by mail.
No the “admin user” does not exist, we have personal accounts and one administrative user called “admin”. This fullname in the useradministration is “admin admin” and not “admin user”
I’d bet that the user is actually User-ID
1 (system user).
Usually Zammad would display
- - in the history unless you rename the
In your case the chosen wording is more than confusing I guess.
The system user appearing in the history is technically correct and caused by e.g. triggers that are sent. Trigger mails are always fired by the system.
Your history doesn’t show the assignment so I guess this is just a wording thing. The assignment is shown within the
April 5, 2023, 6:25pm
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.