Tracker sync.
Your backlog can stay in step with the issue tracker your team already uses. Four ship: Linear, Plane, Dart, and Beads. Every direction has its own switch, and two of the writing directions are off until you turn them on.
01The four providers
Tracker sync lives at Settings → Integrations → Issue trackers, one row per provider. Connect shows only while that provider has no live connection. Once one exists, you add more mappings through Manage.
On the three keyed providers the authorize step lists what Cyboflow uses: read and write on issues, or on tasks in Dart. Comments, attachments, and billing are left alone, and on Dart so are docs. Beads has no network access at all, because it drives the local bd CLI.
Beads is bound to a repository rather than to an account, so its wizard skips the authorize step and opens on Map with one row per Cyboflow project. Each row names the folder Cyboflow probed. Where the probe found a workspace, the row carries a select reading Sync into <project> or Don’t sync. Where it did not, the row offers a fix instead.
- If Cyboflow probed the wrong folder, Point at a folder… repoints that one row, and use the repo folder puts it back.
- Where no workspace exists yet, the row offers Initialize. It sets one up locally with the --stealth config and commits nothing. For shared, git-tracked Beads, run bd init yourself in a terminal.
- A row that failed for another reason, such as a lock timeout, unreadable metadata, or a bd below the supported version, shows its message and a Detect to probe again.
- A missing bd CLI is a fact about the machine, not about each repository, so it is reported once above the rows.
02Connecting
Connecting a keyed provider for the first time runs a six-step wizard: Connect, Map, Tasks, States, Reconcile, Review, labeled Step 01 · Authorize through Step 06 · Confirm. The Beads pass and the add-mapping pass both start on Map and count five.
One pass can create several connections at once. Map points many tracker groups (Linear projects and teams, Plane projects, Dart spaces) at Cyboflow projects, and each mapping becomes a connection of its own.
- Connect
Takes the key and answers with the identity it authorized as.
- Map
Points each tracker group at a Cyboflow project.
- Tasks
Narrows which issues are in scope: All tasks, By assignee, or Manual.
- States
Maps each tracker state onto one Cyboflow target. State mapping has the six.
- Reconcile
Lists backlog rows the target project already has, one ruling each: Keep, Link, or Discard.
- Review
Confirms, then writes each mapping in turn.
Going back never re-fetches. Changing the mappings, or the Tasks selection, invalidates the steps that depend on it and nothing else.
The connected view behind Manage holds a Sync settings card, a Project mappings card, and the last sync log with a Sync now button.
03What syncs, and which way
Auto-sync runs every 5 minutes. The row saying so is a display, not a control: the interval is fixed and the tick has no off switch. Direction is what you set, per connection.
Field write-back only governs the outbound half. Edits made in the tracker still merge into linked items, and this setting never stops that. Inbound merging runs on any pass that runs at all, which is any pass where importing or status sync is due.
Manual defers; Off discards. A direction left on Manual banks its work until you press Sync now, so nothing is lost. Off refuses the write at the moment it would have been queued, and switching a direction to Off also cancels whatever it had already queued.
That is why turning field write-back back on backfills the linked items whose title, description, priority, or category drifted while it was off. Status sync backfills the same way. Neither one touches an item archived while the direction was off.
The same card carries two more controls, above the read-only rows State mapping covers. Mirror task breakdowns files the tasks a Planner run writes as sub-issues of the origin issue. Conflicts is Auto-resolve or Manual review, with the open count beside it.
An Open conflicts card appears whenever anything is waiting, and shows both values side by side with Accept ours and Accept theirs. Auto-resolve picks for you and files the value it discarded as a non-blocking finding, which you triage in Insights.
04State mapping
The States step maps each tracker state onto one Cyboflow target. Defaults come from the state’s own group in the provider, and a pick you make by hand is kept if you leave the step and come back.
- Don’t import leaves that state alone.
- Idea, Ready for development, Done, and Won’t do are the four board stages a tracker may write.
- In development (one way) is asymmetric on purpose, and the option text says so.
In development is derived from what a run is doing, so a tracker is never allowed to place an issue there. Picking it sets the outbound direction instead. The pick names which provider state a task entering In development is pushed to, so the app does not guess at the provider’s first started state.
Imported issues land as ideas. From then on a linked item is merged three ways against the last snapshot Cyboflow synced, so a field counts as changed only where it moved.
Priority and category are mapped in the wizard too: seven priorities, plus three categories on Dart and Beads. Editing any of the tables means running the wizard again.
The connected view reports the mapping tables read-only. State mapping shows a count and the targets in use. Priority mapping shows a count, and so does Category mapping on the two providers that carry categories.
05Several mappings
Several mappings can point at the same Cyboflow project. Only one per provider pushes new ideas outward.
The Map step asks you to pick when one pass points more than one group at the same project and no existing mapping already holds the flag. Otherwise the mapping that already pushes keeps pushing.
The Project mappings card lists every sibling as its own row, each with its own Remove, which asks Remove this mapping? Existing links stay. before it acts. Add mapping reopens the wizard on Map with five steps and never asks for the key again.
The push target can also be moved from that card. A row that is not the push target carries Make push target, which moves the flag onto that row and off its siblings. It is offered on an active row, or on a paused one only where that project has no active sibling at all.
The row that does hold it is chipped Pushes, or Pushes when reconnected while it is paused. Open a mapping that is not the push target and its Sync settings card says so: New ideas push · off, because another mapping for this project pushes.
In add-mapping mode Map is a mapping editor in two halves. The live siblings come first, each with an Unlink that stages a disconnect locally. Below them sit the groups no kept sibling covers, each offered a project select.
A scope is either linked or mappable, never both, so moving one is unlink and then map. A pass that only unlinks skips Tasks, States, and Reconcile, because those steps describe mapped groups it no longer has.
06Removing and unlinking
Deleting or archiving a linked backlog item asks about the remote issue before anything local happens. The dialog is headed with the item’s ref and the trackers it is linked to. It offers two rulings, plus Cancel, which backs out of the removal altogether.
- Keep in <trackers> drops the links and leaves every issue exactly as it is.
- The other button is worded as the action it will perform. It reads Archive in <trackers>, or Mark cancelled in <trackers> where the provider has no archive endpoint or that connection’s archive sync is off. Where the links disagree it reads Archive / mark cancelled.
One item can be synced to more than one tracker, so the ruling is global: it applies to every live link the item has. Deleting an idea carries the same ruling into that idea’s linked epics and tasks, and the dialog says so before you pick.
Picking an answer writes nothing. The ruling is recorded and then the ordinary delete or archive confirm opens, so backing out of that confirm leaves the item, its links, and every remote issue untouched.
Cyboflow never hard-deletes an issue in your tracker. Trashing or canceling one is the strongest thing it will do.
Disconnecting is a separate act. Disconnect on the connection, or Remove on one of its mapping rows, stops the sync and leaves the existing links where they are.