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
Browser + version: Tested on latest Google Chrome (v84.0.4147.89)
Ticket-ID: #1078120
Expected behavior:
When you deactivate a signature, it will also be removed from any group it's configured in.
This causes the agent to no longer be able to get this signature when hitting on "reply" on new articles.
Actual behavior:
When deactivating a signature, Zammad will not remove it from any group it's configured in.
If you now go to any ticket of that affected group and create a new reply, Zammad will still provide that signature.
You have to manually remove the signature configured in that group to solve that issue.
Steps to reproduce the behavior:
go to email -> signatures and deactivate a signature that you know is configured within your group
in default installations this applies to Users group and the default signature
go to groups and check your group configuration
signature is still there
now reload and re-check - still there
go to any ticket in that group and click on reply - you'll see the deactivated signature
Yes I'm sure this is a bug and no feature request or a general question.
The text was updated successfully, but these errors were encountered:
Maybe I'm understanding wrong, but if I set a signature to inactive and create a new reply in the group in question afterwards, would you think it's valid that we still insert the inactive signature there...?
Infos:
Expected behavior:
When you deactivate a signature, it will also be removed from any group it's configured in.
This causes the agent to no longer be able to get this signature when hitting on "reply" on new articles.
Actual behavior:
When deactivating a signature, Zammad will not remove it from any group it's configured in.
If you now go to any ticket of that affected group and create a new reply, Zammad will still provide that signature.
You have to manually remove the signature configured in that group to solve that issue.
Steps to reproduce the behavior:
Users
group and thedefault
signatureYes I'm sure this is a bug and no feature request or a general question.
The text was updated successfully, but these errors were encountered: