New Linear Connection Table: Project History
AnsweredConnector name: Linear
Table name: project_history
API documentation link: https://linear.app/developers/graphql
Additional details:
Requesting that the Linear connector ingest project audit history via the Project.history connection (ProjectHistoryConnection > ProjectHistory nodes). Each ProjectHistory row exposes an entries field (typed as JSONObject in the schema, but in practice an array of change-event objects) that captures every mutation made to a project over time. This is the project-level analog of IssueHistory, which the Linear connector already ingests.
Today Project.status, Project.lead, Project.members, and similar fields only expose the current value and there's no way to reconstruct the historical timeline of how a project evolved without this endpoint. We need the full state-transition history for analytics on project lifecycles, ownership changes, team composition over time, and lead time between stages.
If we could please ingest all available event types present in ProjectHistory.entries[]. Each event is a self-describing object keyed by entries[].type (e.g. status, leadId, members, teams, initiatives, milestones, priority, dates, name, description, etc.) with from / to or added / removed fields as appropriate, plus at (epoch ms), actorId (or actorIds), and a source object indicating whether the change came from a user, OAuth app, or integration.
-
Official commentHi Jalen,
Thank you for the thorough request - the detail on the event types and fields you need made this much easier to assess. We have confirmed that Linear does expose project history through its API, and we have added this to our active backlog. Your read on the entries field is correct: Linear returns it as a single JSON value rather than a structured set of fields, which shapes how we can model it.
One question to help us prioritise the modelling work: would a JSON column containing the raw change events be usable for your analytics, or do you need specific event types broken out into their own columns to make it practical? If the latter, knowing which two or three event types matter most - status transitions, lead changes, team composition - would help.
We will keep you updated on this thread.
Please sign in to leave a comment.
Comments
1 comment