Template schema

Create templatesthat stay portable.

A good template stores reusable intent, not server-specific IDs or private history.

01

Portable fields

Use keys for labels and stacks, plain card descriptions, relative due offsets, and optional assignee placeholders.

02

Fields to omit

Do not export remote IDs, private comments, attachments, stale absolute due dates, or server-specific user IDs by default.