Data library
Issue resolution histories for AI.
Quick answer
Yes, usually. Issue resolution histories — the record of a problem from report to fix, with every comment, status change and outcome — are among the most useful records for AI developers, because they show step by step how teams diagnose and solve problems. A company can license them when it owns the records and removes customer and staff details first.
What's included#
- Original report and steps to reproduce
- Status changes, assignments and priority changes
- Comments, investigation notes and linked fixes
- Resolution type and time to resolve
- Reopened issues and follow-up
Where it typically lives
How AI developers use it#
- Training AI agents to diagnose and resolve problems
- Evaluating whether AI picks the right next step
- Teaching models to summarize long investigations
Preparation and privacy#
- Remove customer names, emails and account numbers
- Replace staff names with consistent stand-in labels
- Remove secrets pasted into comments or logs
- Keep timestamps and status order intact
What's usually left out#
- Security incidents your team chooses to hold back
- Issues tied to clients whose contracts forbid sharing
- Attachments and screenshots not reviewed separately
How it's packaged#
- One record per issue with an ordered event timeline
- A data sheet listing projects, years covered and issue count
What makes it valuable#
- A clear resolution on most issues
- Detailed comments, not just status flips
- Several years of consistent use
Starting with a sample#
- A few dozen resolved issues from one project, cleaned and approved by you
How SourceX approaches it#
Preparation requirements are agreed with you before any work begins, and the approved dataset is delivered only after an executed agreement and your explicit authorization of buyer access.
Industries with this data
Datasets built from this data
Dataset specs AI labs can request through SourceX, sourced to spec from businesses like yours.
- Software and ITSoftware engineering histories (issues, PRs, reviews)A software engineering history dataset is a linked record of how a team changed its code: each issue joined to the commits, pull request, review comments…CodeTextStructured records
- Software and ITProprietary codebases with full historyA proprietary codebase dataset is a company's private source code delivered as whole repositories with their version history: commits, branches, tags and…Code
- Software and ITIT service management and incident historiesAn ITSM ticket dataset is the record of how an IT organization handled its incidents, service requests, problems and changes, exported from its service…TextStructured records
Typical fields#
- Record ID (pseudonymous)
- Created and closed timestamps
- Category or type
- Request or input text
- Ordered steps or actions
- Outcome or resolution
- Role of each actor (not identity)
Sample record
Illustrative · fictional
- record_id
- rec_8f21c0
- created / closed
- 2023-04-11 → 2023-04-12
- category
- Billing question
- request
- Customer [NAME] asks why invoice [ID] was charged twice.
- steps
- 1. Checked payment log 2. Found duplicate 3. Issued refund
- outcome
- Resolved · refund issued
- actors
- customer, agent_tier1
What buyers look for#
- Complete start-to-finish records
- Consistent fields over years
- Clear, labeled outcomes
- Low duplication
- Work done by skilled professionals
- Edge cases and failures, not only successes
Personal details removed#
- Names
- Email addresses
- Phone numbers
- Postal addresses
- Account, customer and order numbers
- Government IDs
- Payment details
- Health information
- IP addresses and device IDs
- Credentials, keys and hostnames
How buyers test it#
- Sample review by buyer researchers
- Residual personal-data scan
- Duplicate and leakage check against public data
- Label and outcome accuracy spot-check
- Rights and consent documentation review
Rules that may apply
Federal Wiretap Act 18 U.S.C. 2511
Applies to recorded calls and intercepted communications; some states require all-party consent. Assessed deal by deal.
California Consumer Privacy Act Cal. Civ. Code 1798.100 et seq.
May apply where records include personal information of California residents and the business meets the law's thresholds. Assessed deal by deal.
Reviewer note: applicability is confirmed with counsel for each deal. Not legal advice.
All data types · Internal knowledge bases · Project records · Sales call transcripts
Frequently asked questions
Are short, one-line issues useful?
Less so. Buyers look for issues with real investigation and a clear outcome, so those are usually prioritized.
Related resources
- IndustryBPO & contact centers data
- IndustryRecruiting & staffing data
- QuestionCan CRM data be licensed?
- QuestionTraining data vs evaluation data: what's the difference?
- SolutionWhat is AI evaluation data?
- SolutionHow AI developers source data
- DataWorkflow data
- DataInternal knowledge bases
- InsightHow much is my company data worth to AI companies?
- InsightHow does AI training data licensing work?
- InsightCan manufacturers sell their data to AI companies?
- GlossaryDataset
See if your company qualifies
A short company assessment. No data uploads are needed.