Silent ticket updates via REST-API

  1. What is your original issue/pain point you want to solve?
    I want to make calculations in a ticket with a 3rd-party-solution via webhook/API.

  2. Which are one or two concrete situations where this problem hurts the most?
    In this case, calculate costs based of accounted time and a hourly rate from an external database. And the PUT /api/v1/tickets/<id>-call is firing agent notifications, even though this “change” is just a calculation result of a previous ticket update.

  3. Why is it not solvable with the Zammad standard?
    There is no way to surpress agent notification on API-updates:
    Update Ticket using rest api while suppressing notifications - Technical assistance - Zammad - Community

  4. What is your expectation/what do you want to achieve?
    Preventing double notifications.

1 Like