Webhooks

The Projects tab also configures service hook subscriptions — Azure DevOps events posted to an HTTP endpoint.

A subscription is per project, so sending workitem.updated from fifteen projects to the same endpoint normally means creating fifteen subscriptions by hand. Charter defines one and applies it to every project you select.

What a subscription needs

• Event type — workitem.updated, build.complete and so on. The available events and their filters are read live from Azure DevOps, so the list reflects what your collection actually supports.
• URL — the endpoint receiving the POST.
• Filters — narrow the event, for example to a single work item type or area path.
• Consumer inputs — HTTP headers, basic authentication, and how much resource detail to send.

The project is not part of the configuration you edit. It is injected per project when the subscription is written, which is what lets one definition apply everywhere.

Filtering by work item type

Where a filter takes a work item type, Charter offers the types present across the projects you have selected, and still accepts a typed value. The underlying filter is matched on the type's name as Azure DevOps stores it.

A warning about endpoints

A webhook sends collection data to whatever URL you give it, and Charter will happily configure that for fifteen projects at once. Check the URL before applying, particularly if it came from a configuration file someone else exported.