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
When forwarding an agent article with a quotation, the agent's name is unintentionally exposed in the quote head, even after changing the Sender Format in the Admin interface to "System Address Display Name" only.
This is the same as for replying described and fixed in #4768.
Expected behaviour
When setting the Sender Format to "System Address Display Name", the agent's name should not be exposed in the quote head, but be replaced by the System Name.
Steps to reproduce the behaviour
Set up a fresh Zammad instance. Go to email settings in the admin interface and set Sender Format to "System Address Display Name".
The steps are the same as in is #4768 but for forwarding instead of replying. It can probably fixed in this file.
Support Ticket
No response
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:
Used Zammad Version
6.2
Environment
Actual behaviour
When forwarding an agent article with a quotation, the agent's name is unintentionally exposed in the quote head, even after changing the Sender Format in the Admin interface to "System Address Display Name" only.
This is the same as for replying described and fixed in #4768.
Expected behaviour
When setting the Sender Format to "System Address Display Name", the agent's name should not be exposed in the quote head, but be replaced by the System Name.
Steps to reproduce the behaviour
Set up a fresh Zammad instance. Go to email settings in the admin interface and set Sender Format to "System Address Display Name".
The steps are the same as in is #4768 but for forwarding instead of replying. It can probably fixed in this file.
Support Ticket
No response
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: