Use the Google Sheets integration to create custom analytics and dashboards for your company.
Set it up
Go to the Google Sheets integration settings and connect Linear to a Google account. This will automatically create a Google Sheet called Linear Issues in your Google Drive. This is a workspace setting, so you can only connect one account per team. To share the data with teammates, update permissions directly on the sheet.If you're looking for a one-time download, you can export a CSV instead.
What data is exported?
- Issue ID
- Team
- Issue title
- Issue description
- Status
- Estimate
- Priority
- Project
- Creator
- Assignee
- Labels
- If the issue is associated with a Cycle:
- Cycle name
- Cycle number
- Cycle start timestamp
- Cycle end timestamp
- Created timestamp
- Last updated timestamp
- Workflow category
- Started
- Completed
- Canceled
- Archived
You can have multiple workflow states in a single category (e.g. In Progress and In Review fall under Started. The timestamp exported reflects when the issue was first moved to that category.
ProTip: For more advanced queries or to build dashboards in your app, look at our 
API and Webhooks.
API and Webhooks.How it works
Data updates hourly. To run an immediate update, open your command line and type
Google to find the Update Google Sheets data command. Alternatively, go to the integration page and click the update now button. To build analytics from the data, import or reference data the sheet Linear created using IMPORTRANGE, VLOOKUP or similar functions.Avoid updating the source sheet as any changes will be overridden. Create analytics in separate sheets. You can rename the sheet without affecting the data or uploads.
What can you build?
Linear users have used the Google integration to build analytics that:
- Track velocity per team member.
- Track issues added mid-cycle to see how often this happens and how it affects performance and percentage cycle completion.
- Combine with Linear's cycle statistics to get a deeper view into individual and team velocity.
- Track the types of work completed and planned. To do this, create custom labels and workflow states in Linear. A common way to do this is to name labels with a prefix or key:value pair for easier filtering (e.g. comp: feature_name or type: feature/bug/etc.)
- Build a Gantt chart for planning or other charts and graphs to show issue progress over time.
- Track bugs more granularly. What percent of open issues are bugs? How many bugs were worked on in a cycle compared to features?
- Track time: Use the timestamp data to measure how long issues remain open or how long it takes an issue to go from start to completion.
Keyboard Shortcuts
Cmd/Ctrl K then Google G then S Open settings