See why work moved, not only which status changed.
Timeline captures selected Linear teams as cited history, including issue context, comments, priority, ownership, status, and project changes. Connect plans to the conversations and code that made them real.
Timeline captures activity from selected Linear teams and treats synced issues and projects as evidence-backed work artifacts.
Linear remains
Linear remains the system for creating, prioritizing, assigning, and moving issues and projects. Timeline does not replace Linear planning or mutate its records through this integration.
Questions
Ask the operating question, not a search query.
01Which ENG issues did the team complete this week?
02Why did the launch project move dates?
03What high-priority work is still blocked?
04Which issue comments changed the implementation plan?
Example
Fictional Acme example, not customer data.
A status change gets a reason
The Acme rollout date holds while an urgent SSO issue needs another validation run. The weekly update needs the cause, not a list of changed fields.
1
Timeline records ENG-241 state, priority, assignee, and comment context.
2
The Acme rollout project update lands in the same chronology as the issue evidence.
3
A cited answer explains the validation dependency behind the schedule.
Result
The update explains why the rollout is waiting while Linear stays authoritative for the plan.
What Timeline saves
What enters the Timeline
01
Issues, titles, descriptions, identifiers, and lifecycle changes
02
Issue comments and distinct observed comment bodies
03
Distinct observed status buckets
04
Distinct observed assignee values
05
Distinct observed priority values
06
Projects and distinct observed project field states
Use it with
Better when the silos meet
Issue to release
Show whether planned work reached review, CI, and release.
Linear+GitHub
Decision to issue
Connect the channel conversation to the resulting project change.
Slack+Linear
Launch readiness
Compare project state with the latest launch checklist and runbook.
Linear+Google Drive
Setup and privacy
Setup overview
01Connect Linear with a person-owned OAuth connection.
02Choose the Linear teams that person is allowed to share.
03Have a Timeline team admin activate the selected sources.
04Configure the signed Linear webhook for exact workflow-state transitions; scheduled reconciliation runs every six hours as a bounded recovery path for polled snapshots.
Permissions and privacy
Timeline requests Linear’s read scope.
The connection owner can share only Linear teams they are allowed to access.
Non-owners cannot browse unshared provider resources through Timeline.
Connection tokens are encrypted at rest and team activation is separate from personal authorization.
Limits
Honest limitations
Review these capture and recovery boundaries before connecting your account.
The first sync captures current issue and project fields, not their earlier field transitions. Status, assignee, priority, and project-change history begins when Timeline starts observing the selected team.
Initial history and every incremental recovery pass are each capped separately at 2,500 issues, 2,500 comments, and 2,500 projects across the complete selected-team set, not per team. A high-volume team can crowd older records or changes from another selected team out of a surface. After a capped incremental batch, Timeline advances that surface’s updated-at cursor to the newest fetched timestamp without persisting a page continuation, so overflowed older changes are not revisited and can be permanently absent.
Scheduled Linear reconciliation runs every six hours. Without webhook delivery, supported issue, comment, and project changes can remain stale for nearly six hours.
The Linear source picker lists at most the first 2,000 teams returned by the API; teams beyond that cap cannot be selected.
Without webhook delivery, reconciliation can miss a move between Linear workflow states that normalize to the same Timeline bucket, such as Backlog to Todo or In Progress to In Review, when no other captured field changes.
Polling retains issue status for at most 5,000 issue IDs. After pruning, a missed reopen webhook can be lost when polling regenerates the original open-state digest.
Linear issue, comment, and project events are keyed by their current captured field digest. If fields return to a previously captured combination, the reversion reuses that immutable row and does not create new chronology evidence.
Only activated teams are captured; unselected Linear work stays outside Timeline.
Timeline records the work history but does not create, edit, assign, or reprioritize Linear issues through this native sync.
Fields outside the supported issue, comment, and project surfaces may not appear as distinct timeline events.
FAQ
Questions, answered
Can Timeline sync only one Linear team?+
Yes. The connection owner shares selected teams, and the Timeline admin activates only the desired sources.
Are issue comments searchable?+
Yes. Captured issue comments become citable history and can support answers alongside issue and project changes.
Will Timeline change our Linear issues?+
No. This native integration reads selected work into Timeline. Linear remains authoritative for issue and project state.
Why combine Linear with GitHub?+
Linear explains the plan and issue movement; GitHub provides implementation, review, CI, and release evidence. Timeline can answer across both without flattening their roles.
