Automation webhooks now include current issue context

Automation webhook deliveries now include the current issue and project context that a receiver needs to route work. New automation actions use schema version 3; subscription broadcasts and ping tests keep their existing schema and queued payloads keep their stored shape.

Current issue context

Issue events include the current title, status, priority, assignee, update time, and safe identifier and URL fields when available. The project includes its ID, name, and slug. Projectless issues keep project: null and use the organization issue URL when Atoll can provide one. CI events keep issue: null and include useful provider, repository, workflow, conclusion, branch, and run URL fields.

Safe trigger details

The trigger identifies the event type and lists sorted public field names for issue changes. It does not include descriptions, bodies, raw before or after values, delivery IDs, or internal run identifiers. CI triggers use an empty changed-fields list. Direct issue artifact links may add compact counts by type; Atoll leaves that optional field out if the authorized lookup is unavailable.

Receiver setup remains one-time

Webhook Settings now explains that a Standard Webhooks receiver secret is already configured, while the Atoll signing secret remains available once under the collapsed Advanced section. Done, Escape, and outside click close the success message without a required acknowledgement.