But the best we can give.
This stuff takes time, yes, if it was me I would have preferred it to be there already, but what can you do.
It’s a free product, you can’t really demand anything? If you want a specific promise of date, contact their sales team and they will probably gladly help if you pay them to make it so, if not, sit back and wait with the rest of us 
And trust me, i want this as much as you do, but comments like that is demoralizing for the team who deliver this for free to us, be appreciative, it is a huge and complicated system we get for free 
FYI: I managed to integrate a barebones (but still very useful) TinyMCE into Zammad with a mix of user scripts (browser console pastes turned into TamperMonkey script) and CSP policy adjustment on reverse proxy.
Looking forward to any improvements and fixes.
For it’s worth, I’ve written a basic javascript addon for Zammad that adds formatting buttons to ticket and knowledge base content editors. See here: Add formatting buttons to content editor
Hopefully it helps make the current situation more tolerable until UI 2.0 is ready.
1 Like
Hi, MrGeneration, not trying to question the fact that rewriting such big parts of a product can take a lot of time, but could you maybe share a quick status update on this?
It has been about 5.5 years since the first message in this thread, so I was wondering if there has been any progress or if the idea is still on the roadmap.
In the meantime, would it make sense to adopt the workaround proposed by kdn, at least temporarily? Or would that be a bad idea from the maintainers’ perspective?
You might want to take a quick look in the release notes of Zammad 7.0 which added a small subset.
Apart from that, the I covered the state as of 8months ago here. Since then it evolved further, but some things just take time unless you want to stop developibg anything else. I can‘t give you more insight, as I‘m no longer a Zammad employee.
1 Like
And the real development started not 5.5 years ago.
1 Like