Connecting a tracker closes the loop on follow-through. Action items created in a retro can be exported to your tracker as issues, and SmartRetro cross-checks their status daily — so an item marked done is verified against the tracker, not just self-reported.
Connecting
In Settings → Integrations, open the tracker card and connect your provider. Linear connects over OAuth: authorize SmartRetro, then choose which Linear team exported issues should land in — the selection is explicit, so items never go to a surprise team. Once connected the card shows the provider, the auth method, and the target team.
Jira connects over Atlassian OAuth. One Atlassian authorization can span several sites, so setup includes picking the site to use, then mapping Jira projects to your teams. Because issue creation in Jira depends on each project’s required fields, export unlocks once you’ve chosen a default project and completed the field mapping — the card walks you through it. If a connection hits a problem — a revoked token, a permissions change — the card flips to “Connection error” or “Action needed” with a message telling you what to fix.
Exporting action items
From an action item, export it to the connected tracker and SmartRetro creates the issue, keeps a link back to it, and records the export so the same item can’t be exported twice. See Action items.
Completion is cross-checked
Once an item is linked to a tracker issue, SmartRetro checks that issue’s state daily. If the tracker shows the work merged or closed, the item is flagged as externally completed so you can confirm it in SmartRetro. When SmartRetro’s status and the tracker’s disagree, that mismatch becomes a signal in the feed rather than being resolved quietly — the point is that “done” is trustworthy.
Disconnecting
Disconnect from the tracker card at any time. Exported issues already in your tracker are unaffected; SmartRetro simply stops syncing.
Next
Trackers pair naturally with a code host for delivery signals. For what’s stored, see Trust & security.