parent_card_ref, the child is child_card_ref. The links must not form a cycle (a card cannot be its own ancestor). Write each pair once, from the parent side.resource_files of the manifest, with "resource": "card_children". An entity can have any number of files. See Bundle format.[
{
"resource": "card_children",
"path": "resources/card_children.json"
}
]| Field | Type | Required | Description |
|---|---|---|---|
external_id | string (ExternalId) | Yes | Your own identifier of the record, for example k-mrr, unique within the resource across all of its files and case sensitive. Other records refer to this one by it.Constraints: 1–512 characters. |
child_card_ref | Ref<cards> refers to Cards | Yes | The child card, for example a task of the epic. Give the external_id of a cards record.Rule: Differs from parent_card_ref. |
parent_card_ref | Ref<cards> refers to Cards | Yes | The parent card, for example an epic. Give the external_id of a cards record. |
created_at | Timestamp | No | When the child was linked to the parent, with a time zone, for example 2026-01-12T09:30:00Z. Decides where the child appears on the parent card's chart: as part of the initial scope if linked before the chart starts, or as added work on the day it was linked.Constraints: RFC 3339 with a time zone. Default: |
{
"external_id": "cc-nrr-churn",
"parent_card_ref": "k-nrr",
"child_card_ref": "k-churn"
}