Gerrit

@Suhopoljac this issue is not about that. It's about the possibility to disable options in a tree select via object manager, rather than Core Workflows.

@ozturkinc I see your point. But your suggestion is about the design of the tree select, this issue is about an option in the admin interface. Please use the community...

@rolfschmidt what you are talking is again a different issue: https://github.com/zammad/zammad/issues/5019

To be sure, this issue is about something like this:  

Hosting would also benefit from separating the input fields. Because this way, hosted customers could change the display name of the notification sender without adjusting the (in hosted) fixed e-mail-address....

Please also add `ui_ticket_zoom_sidebar_article_attachments` to https://docs.zammad.org/en/latest/admin/console/hidden-settings.html It activates this sidebar button: 

As discussed previously (don't know who was involved), ES supports search result relevance: https://www.elastic.co/guide/en/app-search/current/relevance-tuning-guide.html I think we should utilize this for the knowledge base. For tickets it makes sense to...

There is also a FR in the community now: https://community.zammad.org/t/replace-macros-triggers-and-scheduler-with-a-combined-workflow-system/13495/2

> Messages sent from incorrectly configured Microsoft Outlook/Exchange email clients may contain a file attachment called winmail.dat. This attached file contains formatting information for messages that use Microsoft's proprietary TNEF...

**Refinement 30.08.2024** Agreed on the following solution: - Instead of using the customer of the source ticket as a pre-fill for the ticket creation mask, we will use the author...