Working with your tracker

Connecting a tracker is covered in Get started. This guide is about ongoing use — what to link, what not to link, and how to handle drift.

What to link, what not to link

Link cards that represent real tracker items (stories, tasks). Don’t link discussion cards, parking-lot cards, or open questions — the tracker is for committed work.

Who can edit tracker-linked cards

Member-only for tracker writes

Editing a tracker-linked card — changing the title, status, or any field that pushes to ADO or Jira — requires the user to be a workspace member. Guests can view, comment, and react on linked cards, but the moment an edit would propagate to your tracker, it’s blocked.

This is by design: every write to your tracker is recorded with the CardBoard member who made it. If a guest needs to edit synced cards, invite them as a member, or have a member make the change on their behalf.

Field mapping

Title and status are standard. Custom field mapping is configured per board. Don’t re-map a working board casually — it can rewrite a lot of card state.

Conflict resolution

When CardBoard and the tracker both change at once, the first write wins and the second gets a notification with the latest state.

Tracker reorganization

If someone moves a work item to a different project or changes its type, CardBoard re-syncs and broken links surface on the board.

Migrating off a tracker

Disconnecting a board keeps cards, outcomes, and comments; it loses tracker IDs and sync history. Decide whether to migrate or start fresh.

Troubleshooting

“I tried to edit a tracker-linked card and got a permission error.” Check whether the user is a workspace guest (rather than a member) and whether the card is linked to a tracker. Guests can edit cards freely, but tracker-linked cards require member status.