Which webhook events trigger automated changelog generation?

`sprint_closed` in Jira, `cycle_completed` in Linear, and `release: published` in GitHub. Each triggers a scoped background generation job.

Does auto-sync immediately publish the changelog publicly?

No. Auto-sync generates a pending draft in your Soobrief workspace. A designated owner receives a notification to review and approve before publication.

What happens if a sprint closes with incomplete carried-over tasks?

Carried-over tasks lack a completion timestamp within the closed sprint window, so they are automatically excluded from the generated release notes.

Can a sprint auto-sync trigger custom webhooks on completion?

Yes. Once the draft is approved and published, downstream Slack, Discord, and custom API webhooks fire automatically.

Sprint and Milestone Auto-Sync: Drafting Updates on Release

Trigger changelog drafts automatically whenever a sprint closes in Jira/Linear or a milestone is tagged in GitHub.

Soobrief Team — Product & Engineering, Sooapps · 2026-09-10

In short

Sprint and Milestone Auto-Sync automatically compiles a complete draft changelog the moment a sprint closes in Jira/Linear or a release milestone is tagged in GitHub. By converting closure webhooks into background generation triggers, teams arrive at their review meeting with release notes already written.

The worst time to write release notes is an hour before sprint demo. Everyone is stressed, rushing to verify staging builds, and nobody wants to spend forty minutes writing markdown.

1. Event-Driven Milestone Triggers

Instead of relying on human memory to initiate generation, Soobrief listens to closure webhooks:

Jira: sprint_closed event.
Linear: cycle.updated where data.status == "completed".
GitHub: milestone: closed or release: published.

When received, an asynchronous job locks the sprint boundaries and queries all completed tasks attributed to that milestone.

2. Draft Creation with Zero Human Effort

The worker applies deterministic grouping, calls the configured narrative LLM, and creates an editable draft under the workspace notes dashboard.

The engineering lead receives an immediate notification: *"Sprint 42 changelog draft is ready for review."* All that remains is a quick sanity check and a single click to publish.