Sunset an API version without breaking customers — announce, monitor remaining traffic, migrate stragglers, and only then remove the old surface.
API and platform teams retiring endpoints on a deprecation timeline.
Quick answer
The API deprecation template is a ready-made workspace for API and platform teams retiring endpoints on a deprecation timeline.
API deprecation template in short
Included when you apply it
Applying this template creates the 1 board below — with every list — and pre-loads 3 sample issues, all yours to edit. The automation rules further down are suggestions you can wire up next; they aren't created for you yet.
A preview of how this template lays out — the boards, their custom workflow states, and where the sample issues land. WIP caps show a badge.
Deprecations
Deprecate /v1/issues in favour of /v2/issues
Sunset date set 90 days out; add Deprecation header now.
Email top-10 API consumers still on the legacy auth flow
Add Sunset + Deprecation response headers
These rules aren't created when you apply the template — they're recipes you can wire up in Settings → Automations once your board exists.
When
Deprecation moves to 'Announced'
Then
Add a Deprecation header and email every active consumer of the endpoint
When
Endpoint reaches 'Zero traffic'
Then
Notify the owner that it is safe to schedule removal
Ready to spin this up?
Sign-up takes seconds. We build this template's boards, lists, and sample issues in your new workspace, all yours to edit.
FAQ
Sprint planning
A cycle-driven sprint board with WIP limits, estimates, and PR-linked issues — the default starter pack for product engineering teams.
View templateBug triage
An intake-to-resolution pipeline that separates triage from active fixing, with severity labels and reproduction notes on every card.
View templateRelease checklist
A repeatable release runbook as a sub-issue tree — cut, verify, ship, announce — so nothing ships half-checked.
View template