Linear Integration
The Linear integration syncs your issues, projects, and cycles into Barvol so you can track engineering progress alongside your goals and customer context — without duplicating your workflow in a second tool.
What Barvol reads from Linear
Barvol reads from the Linear teams and projects you authorize. Synced data includes:
- Issue titles, descriptions, status, priority, and assignee
- Project and cycle names, dates, and progress
- Label names applied to issues
- Issue creation and completion timestamps
- Relation links between issues (blocks, duplicates)
Barvol does not read issue comments, attachments, or private team settings.
Connecting Linear
Go to Integrations, click Linear, and click "Connect." Authorize the Barvol Linear app with your Linear account. You will be shown a list of Linear teams to sync — select the teams whose issues are most relevant to your Barvol workspace.
After connection, an initial sync imports the last 90 days of issues from each selected team. Ongoing sync runs every 10 minutes.
Linear issues in the Tasks view
Linear issues are surfaced as read-only entries in the Barvol Tasks view alongside your native Barvol tasks. They are visually distinct — labeled with the Linear logo — so you can tell them apart. You cannot edit Linear issues from Barvol; all changes are made in Linear and synced back.
This gives you a single view of everything in flight — Barvol tasks and Linear engineering issues — without managing two separate systems.
Linking Linear projects to Barvol goals
You can link a Linear project or cycle to a Barvol goal. When linked, the goal detail page shows:
- Total issues in the linked project and how many are complete
- Percentage progress based on issue completion
- Overdue issues (issues past their due date that are still open)
- Recent issue activity (what moved to done in the last 7 days)
This makes engineering goals directly trackable without manual status updates.
Asking about Linear data
Use the AI chat to query your Linear data:
- "What issues are blocking the current cycle?"
- "Which high-priority bugs are still open?"
- "How much of the current sprint is complete?"
- "What did we close in Linear last week?"
- "How many issues were opened vs. closed this month?"