Title: Stop communications with enabled maintenance mode
- What is your original issue/pain point you want to solve?
Enabling maintenance mode has only an affect on non administrative sessions, however, if you want to restructure Zammad and have a fair amount of email channels, you’d have to disable all channels to achieve a “communication silence” to re-configure your system structure, groups and routings in piece. - Which are one or two concrete situations where this problem hurts the most?
The maintenance mode sounds like it does more (than it does and that’s advertised) as a maintenance usually means that you don’t want data to be changed - not just from agent perspective. - Why is it not solvable with the Zammad standard?
The maintenance mode only kicks off non administrative sessions. - What is your expectation/what do you want to achieve?
Maintenance mode should (optionally?) also disable communication channels to allow actual data and routing maintenances without changing productive data in Zammad. (This allows you to fuck up a configuration and take a snapshot to restore - that’s not possible if communication data is being changed).
Your Zammad environment:
- Average concurrent agent count: 10
- Average tickets a day: 200
- What roles/people are involved: Admins, Agents, Customers
Anything else which you think is useful to understand your use case:
-
