Skip to content

License your Jira and issue tracker history for AI training

An issue tracker is an engineering team's diary. Linked to the commits and reviews that closed each ticket, it trains coding agents.

Price Index, Q4 2026
  • Shut-down startup, code and workspace$10,000 to $100,000 per companyMedium confidenceGizmodo, Apr 2026
  • Operating company, 30+ staff, English records$185,000 to $1M+ per companyMedium confidenceRightmark summary of public company data programs, 2026
AI-generated footage

Jira, Linear and GitHub issue history can be licensed to AI labs building engineering agents, usually with the code that resolved each ticket or as part of a company archive. Private repos fetch $150 to $1,500 per sale, and full company archives are listed at $185,000 to $1M+ in the US. Tickets linked to commits and reviews earn the most.

  • AI companies are buying old work chat messages, emails and project records as training data. Forbes, (opens in a new tab)
  • Private repos typically license for $150 to $1,500 per repo per sale (indicative). Rightmark,
  • Published buyer programs put an operating company archive at $185,000 to $1M+ per company. Rightmark,

Updated

Timeline
2 to 13 weeks
from signing to payment, after screening and a data inventory (inferred from published steps)
You keep
Ownership
Lump sums are usually exclusive for a term; a revenue share is non-exclusive.

Why AI buyers want it

Coding agents must go from a vague ticket to a merged fix. Tickets linked to commits and reviews show that path end to end, and buyers grade archives by how well those links hold. Every bug, request, estimate and change of plan is in the tracker.

Think of it this way

A ticket linked to its fix is a worked example with the answer key attached.

What sets the price

  • Tickets linked to commits and pull requests.
  • Comments and discussion on each ticket.
  • Years of history across many projects.
  • Workflow data: estimates, sprints and bug triage.

Most valuable when linked to the repos that resolved the tickets. The estimate on this page prices tickets with their linked code from a mid-sized software team.

What blocks a deal, and the fix

Client names and confidential details in tickets
Filtered or masked; client-confidential projects can be excluded.
Attachments with personal data
Excluded or scanned before delivery.
Tickets that point to code you do not own
Link only repos you can license. Tickets about client repos need the same written client consent as the code.

What owners overlook

  • Tickets without code are worth far less than tickets with the fix attached.
  • Rejected and duplicate tickets are useful too: they teach triage.
  • Closed and archived projects count. Keep them in the export.

Market evidence

  • Published programs use work management tools to learn how work is broken down, tracked and finished, and code linked to tickets to learn engineering workflows.Rightmark,
  • Startups that are shutting down have licensed chat, email and project records as AI training data.Gizmodo, (opens in a new tab)

How a deal works

  1. Appraise

    Answer a few questions about what you have. See what affects the price and whether an indicative range is available. No files, no access.

    About a minute

  2. Verify title

    We confirm the company controls the archive, check personal data and third-party rights, and assemble the ownership pack the deal needs.

    Before any offer

  3. Route

    The archive goes to the route that fits it: an exclusive lump sum for a term, or a non-exclusive revenue share.
  4. Sign and get paid

    You approve the agreement and its scope before anything moves. We never hold your passwords: transfers use scoped, revocable connections your admins approve, or exports.

    Payment about 2 to 13 weeks after signing

Questions

How much is Jira data worth?

Issue history is usually licensed with the code it describes or as part of a company archive, not alone. Private repos fetch $150 to $1,500 per sale, and full company archives are listed at $185,000 to $1M+ in the US. Tickets with linked code, as in the estimate on this page (One archive: 40 staff, 6 years, 2 tool types), come to $200,000 to $380,000 at Medium confidence. Indicative estimate, not an offer.

Sources: Rightmark, ; Rightmark,

Is issue tracker data useful without the code?

Yes, but less so. The best deals link each ticket to the commits and reviews that closed it.

Which trackers do you support?

Jira, Linear, GitHub and GitLab issues, Azure DevOps and most tools with a full export.

What gets removed before delivery?

Personal details such as names and contact details, credentials and secrets, and client identities, plus any project you exclude. Client-confidential projects can stay out entirely.

Do you need our tracker admin password?

No. We never hold your passwords. Your admins export the data or approve a scoped, revocable connection for a one-time transfer.

What do we warrant about tickets that mention clients?

That you own or control what you license. Client names and confidential details are masked, and projects that a client contract or NDA restricts stay out unless the client consents.

Get an indicative range for your Jira, Linear and GitHub issues.

About a minute to appraise. No files, no access.

Find out what your data could be worth.

Start with an indicative appraisal. No files or system access needed.

Appraise your data

What brings you to Rightmark?