Recipe catalog / ticket-match
Compare support tickets
Do firstTicket and secondTicket describe the same underlying reported issue?
You want to check whether two tickets describe the same underlying issue.
Explore this recipe interactively ยท Source and implementation guide
Use ticket-match in TypeScript
Install with npm install jev-recipes. Requires Node.js 22.9 or newer and ES modules. Set TYPESAFE_API_KEY in your server environment for live calls, which send input to TypeSafe and use API quota. See the installation guide.
import { ticketMatch } from 'jev-recipes/ticket-match';
const result = await ticketMatch({
"firstTicket": "My workspace export fails with error EXPORT_TIMEOUT.",
"secondTicket": "Exports also time out with EXPORT_TIMEOUT in another workspace."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| firstTicket | string | Required |
| secondTicket | string | Required |
| context | string | Optional |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"firstTicket": {
"type": "string"
},
"secondTicket": {
"type": "string"
},
"context": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"firstTicket",
"secondTicket"
]
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"model": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"input_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"output_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"input_tokens",
"output_tokens"
],
"additionalProperties": false
},
"status": {
"type": "string",
"enum": [
"ready",
"review"
]
},
"verdict": {
"type": "string",
"enum": [
"same_issue",
"related",
"different",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"same_issue",
"related",
"different",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"same_issue",
"related",
"different",
"unclear"
]
}
},
"required": [
"model",
"usage",
"status",
"verdict",
"confidence",
"probabilities"
],
"additionalProperties": false
}
}Saved example result
This hand-authored response demonstrates the contract. It is not a model accuracy measurement. Run it without an API key: npx jev-recipes demo ticket-match.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "related",
"confidence": 0.96,
"probabilities": {
"same_issue": 0,
"related": 1,
"different": 0,
"unclear": 0
}
}
Evaluation evidence
No verified live accuracy measurement is available. Evaluate representative cases before using this decision in your workflow.
Use the evaluation guide to measure this decision on your own labeled cases.
Limitations
- Does not merge tickets or establish a shared root cause from similar symptoms alone. Compare exact identifiers in code.
Related recipes
- incident-match: Use incident-match to select a known incident for one ticket.