Pause / Stop channel fetching during enabled maintenance

Feature requests
1

Title: Stop communications with enabled maintenance mode

  1. 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.
  2. 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.
  3. Why is it not solvable with the Zammad standard?
    The maintenance mode only kicks off non administrative sessions.
  4. 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:
-

10 Likes
2

I like the suggestion, it saves a lot of clicking.

It also prevents you from forgetting to switch on the email channels afterwards.

1 Like
3

Title: Maintenance mode - auto disable channels

  1. What is your original issue/pain point you want to solve?
    While doing updates / making changes in maintenance mode sometimes rollbacks are needed.

  2. Which are one or two concrete situations where this problem hurts the most?
    I would like to have all channels disabled so that no new tickets come in that might accidentally get lost in a rollback.

  3. Why is it not solvable with the Zammad standard?
    It is definitely doable to disable the channels manually each, but having it all rolled into an on-off switch in the maintenance mode.

  4. What is your expectation/what do you want to achieve?
    A one stop shop for locking down communication in and out of zammad until maintenance mode is disabled.

If there is any more useful information, feel free to share it all (e.g.: mockup screenshots, if something is UI related, or the API URL/documentation URL for a service you need a connection to).

Your Zammad environment:

  • Average concurrent agent count: 4
  • Average tickets a day: 30 - 60 depending on the time of year.
  • What roles/people are involved: tech / teachers & faculty

Thank you and have fun.

1 Like