ticket-normalizer

ticket-normalizer

Transforms raw Jira issue objects into the normalised InternalTicket format consumed by domain-router and dependency-mapper.

InternalTicket Schema

{
  "id": "PROJ-123",
  "title": "Add user authentication endpoint",
  "description": "Plain text, max 500 chars",
  "type": "Story",
  "labels": ["api", "auth"],
  "components": ["backend"],
  "links": [
    { "type": "blocks", "targetId": "PROJ-124" },
    { "type": "is blocked by", "targetId": "PROJ-120" }
  ],
  "priority": "High",
  "assignee": "[email protected]",
  "domainSignals": []
}

Field Mappings

InternalTicket field	Jira source
id	issue.key
title	issue.fields.summary
description	issue.fields.description — ADF to plain text (see below)
type	issue.fields.issuetype.name
labels	issue.fields.labels
components	issue.fields.components[].name
links	issue.fields.issuelinks — see link normalisation below
priority	issue.fields.priority.name (null if unset)
assignee	issue.fields.assignee.emailAddress (null if unassigned)
domainSignals	Empty array — populated by label-classifier

ADF to Plain Text

Jira Cloud returns description in Atlassian Document Format (ADF). Extract plain text by:

1. Traverse doc.content recursively
2. Collect all text node values
3. Join with a single space
4. Truncate to 500 characters

If description is null or not ADF, use an empty string.

Link Normalisation

Map Jira link types to internal types:

Jira type.inward / type.outward	Internal type
"blocks" / "is blocked by"	blocks / is blocked by
"relates to"	relates to
All others	relates to

For each link in issue.fields.issuelinks:

• Use outwardIssue.key when the outward relationship is present
• Use inwardIssue.key when the inward relationship is present
• Emit one { type, targetId } object per link

Output

Array of InternalTicket objects, one per raw Jira issue.