Documentation
Field ownership.
Two shores, each still itself. Exactly one thing crosses the bridge — the task — and it crosses precisely. This page is the boundary, field by field.
The model
Mirrored text flows one way, from Linear into the Todoist mirror. Your personal planning fields in Todoist are never read for decisions and never written. The only two-way surface is the active/completed lifecycle, brokered under rules you chose per team.
The ownership table
| Owner | Fields | Bridge behavior |
|---|---|---|
| Linear | Identifier, title, description, assignee, team, project, workflow state, engineering labels, delivery deadline, source URL. | Mirrored from Linear into Todoist. Editing the mirror never updates these fields — reconciliation restores mirrored text from Linear. |
| Todoist | Planned date, reminders, personal priority, ordering, personal labels, private comments, personal subtasks. | Never included in any Todoist update TaskBridge makes, and never mapped to a Linear deadline or any other Linear field. |
| Explicit control | Completion and reopening. | Completion can transition an issue only to the state configured for its team. The prior Linear state is recorded and is the only reopening target. |
Edge semantics
A mirror task goes missing
When a linked Todoist task is absent from the active-task list,
reconciliation probes it directly rather than assuming. A returned
completion can trigger only the configured Linear completion
transition. Only a Todoist 404 tombstones the link — and a
tombstone never deletes or edits the Linear issue.
A mirror task is renamed
A Todoist title edit may be restored from Linear on reconciliation. It can never rename the Linear issue.
The issue becomes ineligible
Issues that have been deleted, unassigned, canceled, or archived are rejected as completion sources and are never completed by the bridge.
What is never synchronized
These are product decisions, not missing features:
- No generic bidirectional field synchronization, and no workflow/field-mapping builder. Bridge configuration is exactly two lifecycle questions per Linear team.
- No Linear title, deadline, or delete mutation of any kind.
- No Todoist-to-Linear issue creation.
- No per-status mirroring of every Linear workflow state — only Todoist’s active/completed lifecycle is synchronized.
- No deletion of anything in either provider. Deleting a bridge removes configuration and history only.