Project Management

How to Use Linear with Zo

Linear is fast and opinionated — which is why developers like it. But managing issues still means context-switching: opening Linear, scanning the board, updating statuses, writing comments, grooming the backlog. Connect Linear to Zo and do all of that from the same place you write code, check email, and manage everything else.

Connect Linear

Go to Settings > Integrations > Linear and authorize Zo to access your workspace. Your Zo can read issues, create new ones, update statuses, add comments, and track sprints.

Check your work at a glance

Instead of opening Linear and scanning the board, ask:

  • "Show my open Linear issues"
  • "What's in the current sprint?"
  • "List all high-priority bugs assigned to me"
  • "What issues did I close this week?"
  • "How many issues are in each status column right now?"

For quick status checks during the day, this is faster than switching to the Linear app. From SMS or Telegram, text "What's left in my sprint?" and get an instant snapshot without opening your laptop.

Create and update issues

Manage issues from chat instead of filling out forms:

Create issues:

  • "Create a bug report: search results page crashes when query is empty. Priority: high."
  • "Create a feature request: add dark mode support to the settings page. Assign to me."
  • "Create an issue: refactor the auth middleware to use the new token validation pattern. Label it tech-debt."

Update existing issues:

  • "Move issue ENG-142 to 'In Review'"
  • "Add a comment to ENG-98: 'Blocked on API changes from backend team — ETA next Tuesday'"
  • "Assign ENG-200 to me and set priority to urgent"
  • "Close ENG-175 — the fix shipped in today's release"

Batch updates:

Prompt

Move all my "In Progress" issues that haven't been updated in 5 days back to "Todo" and add a comment noting they were auto-moved due to inactivity.

Sprint planning with AI

Sprint planning usually means the team staring at a backlog, estimating effort, and dragging issues into the sprint. Your Zo can do the prep work:

Prompt

Look at my Linear backlog. Show me the top 15 issues sorted by priority. For each one, give me the title, priority, any blockers, and an estimate of complexity (small, medium, large) based on the description. Suggest which ones should go into next sprint if we have capacity for about 30 story points.

Prompt

Check the current sprint. What's the total estimated effort? How much has been completed? Are we on track to finish by end of sprint? Flag any issues that are at risk of not being completed.

This doesn't replace the planning meeting, but it gives you a starting point so you're not staring at a cold backlog. Walk into planning with a pre-sorted, pre-estimated shortlist.

Standup prep

Morning standups work better when everyone shows up prepared. Instead of trying to remember what you did yesterday:

Prompt

Prep my standup: what Linear issues did I work on yesterday? What's on my plate today? Are there any blockers?

Your Zo checks your issue activity, reads comments and status changes from the last 24 hours, and gives you a clean summary you can read directly in standup.

For automated standup reports:

Prompt

Create a daily agent that runs at 9am. Pull my open Linear issues, group them by status (todo, in progress, in review, done). Highlight any that changed status since yesterday. Email me a standup-ready summary.

Backlog grooming

The backlog is where issues go to be forgotten. Without regular grooming, it becomes a graveyard of outdated feature requests and stale bugs. Your Zo can do the triage pass that nobody wants to do:

Prompt

Show all unassigned issues in my backlog, grouped by project. For each one, tell me: is it still relevant based on the description? Has it been there more than 30 days? Does it overlap with any other issue?

Prompt

Find issues that haven't been updated in over 2 weeks and summarize their status. Flag any that should probably be closed.

Prompt

Go through my backlog and suggest labels for any unlabeled issues based on their title and description.

Prompt

Look at my backlog and recommend which 5 issues I should tackle this week based on priority, dependencies, and estimated effort.

Running a backlog grooming pass weekly keeps your Linear workspace clean and your sprint planning faster.

Turn emails and conversations into issues

Work often arrives through email, Slack, or conversation. Instead of manually creating issues from context scattered across tools:

  • "The email from QA about the login bug — create a Linear issue from it with the details. Priority: high. Assign to me."
  • "Create a Linear issue from this: 'The checkout page doesn't handle expired credit cards gracefully — users get a blank screen instead of an error message.'"

Combine with Gmail for automated issue creation:

Prompt

Check my Gmail for emails from @qa-team.com from the last 24 hours. For any that describe a bug, create a Linear issue with the email subject as the title and the email body as the description. Label them "from-email" and assign to the QA triage queue.

Cross-reference with other tools

Linear issues don't exist in isolation. They connect to documents, calendar events, and communication channels:

Linear + Notion:

Prompt

Pull my open Linear issues and update my Notion sprint board to match. Add any new issues and update the status of existing ones.

Linear + Calendar:

  • "Check my Linear for this sprint's deadlines. Add them to my Google Calendar as all-day reminders."

Linear + email:

Prompt

Create a weekly agent that runs Friday at 4pm. Summarize my Linear activity for the week: issues created, completed, and in progress. Include any blockers. Email the summary to my manager.

Weekly engineering reports

Generate reports from your Linear data without spreadsheets:

Prompt

Create a weekly agent that runs Monday at 8am. Scan my Linear workspace: - Issues completed last week (by team member) - Issues currently in progress - Backlog items that are unassigned, unlabeled, or stale (no updates in 14+ days) Send me a triage summary via email with recommended actions for each stale item.

Prompt

Generate a sprint retrospective summary: what did we complete, what rolled over, what was added mid-sprint, and how did our actual velocity compare to the plan?

These reports turn Linear from a task board into a data source for team health and velocity tracking.

Getting started

Connect Linear in Settings > Integrations and check your sprint:

Prompt

Show my open Linear issues and tell me which ones are blocking

From there, try creating an issue from chat, running a backlog grooming pass, or setting up an automated standup report. The less time you spend in Linear's UI, the more time you spend actually building.

More from the blog

How to Use Linear with Zo | Zo Computer