Linear issue and project histories: how fractional CTOs combine them with older records

What a Linear workspace holds

Linear organizes engineering work into teams, issues, cycles, projects and initiatives. Each issue has a status path, an assignee, labels, estimates, linked pull requests, comments and, often, a description that explains the reasoning. Project updates add a running narrative of what shipped, slipped or changed.

For a fractional CTO, that structure is the appeal. Issues move through defined states and end in outcomes: shipped, cancelled, duplicated, deprioritized. Together with the linked code review, they show how a team plans, argues about scope and finishes work. That kind of multi-step, outcome-labelled record is thin on the public web, which is why AI developers who train coding and planning agents look for it inside companies.

The depth problem

Software teams often reach Linear from another tracker such as Jira, Asana or spreadsheets, so the history may start at the switch date. The realistic question is not "does Linear have good data" but "what sits behind it."

If the company moved from Jira, ask whether the old instance still runs. Many do, read-only, long after a migration. The guide on Jira Service Management request and SLA histories shows how service-style Jira data looks, and the Smartsheet project and PMO brief covers a different project record that often predates Linear.

The Linear chain check

Run it in the next architecture or roadmap conversation.

• Start date: when did each team begin using Linear, and which tool was used before?
• Predecessor: is the old tracker still reachable, and can an admin export it?
• Links: do issues point to pull requests, incidents and customer tickets?
• Content: do descriptions and comments contain real reasoning, or are they one-liners?
• Rights: does the company own the work, with no client-owned repositories or code mixed in?
• Sponsor: can you reach the CEO, CFO or an authorized representative?

Rights and confidentiality in engineering records

Engineering records carry specific risks. Issues may quote customer data, secrets or credentials pasted into comments. Work done under client contracts may belong to the client. Open-source contributions and third-party code carry their own licenses. Employee names and comments raise notice and policy questions.

Redaction and de-identification requirements are agreed with the company before any work begins, and nothing is delivered without an executed agreement and the company's authorization. This is general information, not legal, tax or financial advice. The company's counsel should confirm rights before a license.

A company that mainly builds software for clients under work-for-hire terms, with no consent from those clients, is a red flag. Fractional CTOs who also serve as architects of record should say so early rather than learn it during scoping.

Export realities, stated generically

Linear offers ways to export issue data, and an API for programmatic access, but available formats, fields and limits change over time and vary by plan. Do not tell a client what can or cannot be exported. Ask the workspace admin to check current Linear documentation and list on the inventory what is exportable, including comments, attachments and project updates. The company's own team runs any export.

When to raise it as a fractional CTO

The fractional CTO referral overview explains the role-level view. For records beyond engineering, Freshservice service desk histories and project-history data show what companies often hold alongside issue trackers.

How the introduction works

1. Register as a partner. Pass your referral link to the founder or CEO, or submit the company through the referral form.
2. SourceX reviews size, history, data breadth and rights with the sponsor.
3. An engineering lead lists Linear, the predecessor tracker and the code host with start dates, using the data inventory builder.
4. Price and terms are agreed before any buyer sees material.
5. AI labs and data buyers review the opportunity.
6. After signing, data is delivered under the agreed redaction rules and the company is paid.

Partners make introductions and give basic fit information only. The fit baseline is on the who qualifies page.

Rewards for a fractional CTO

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is a share of SourceX's fee and never deducted from what the company receives. Check your client engagement terms and any conflict-of-interest policy before registering, and read the program terms.

When Linear history is not enough

• The company adopted Linear recently and has no predecessor records.
• Most work is for clients who have not consented to licensing.
• The workspace was pruned or archives deleted.
• No engineer or admin can run an export.
• The company is below the 50+ full-time employees at peak baseline.

Next step

Ask one client when each team started on Linear and what it replaced. If the chain is long, register as a partner and make the introduction.