Engineering work lives in GitHub. Customer-facing work lives in Lattica. Keeping them in sync without a janky cron job is what this integration is for.
GitHub: pull request linking
Mention a Lattica task ID in a PR title, body, or commit message — LAT-1284 — and the integration links them automatically. The task gets a small GitHub icon next to its title, and the PR’s status shows up on the task: Draft / Open / In review / Merged / Closed.
Closing a PR with merge auto-closes the linked task if the task is in a status configured to close on merge. By default that’s just the In progress column on engineering projects.
GitHub: issue sync
You can sync a GitHub issue and a Lattica task bidirectionally. Title, description, and status flow both ways; comments are mirrored with attribution. Use this when your team genuinely lives in both — for example, an open-source project where contributors are in GitHub and your internal team is in Lattica.
Setup
- Settings → Integrations → GitHub → Install
- Authorize the GitHub App on your organization
- Pick the repositories to connect
- For each repo, choose Link only or Bidirectional sync
Linear: one-way import
If you’re migrating from Linear, the Linear integration runs a one-time import of your workspace, mapping teams to projects and issues to tasks. Comments, labels, assignees, and statuses come over. Cycles map to Lattica’s milestones.
The import is read-only — Lattica does not write back to Linear. After import, decide whether to keep both running in parallel or fully cut over.
Limits and gotchas
- GitHub task IDs in PR descriptions are matched case-insensitively but must include the project prefix (
LAT-not bare1284). - Lattica respects GitHub’s draft state — draft PRs don’t trigger task closure.
- Bidirectional sync uses GitHub’s webhook delivery; if GitHub has an outage, sync resumes when their webhook queue clears.