Iteration cards

Puts a card into an iteration (sprint), including iterations that are already closed. Write one record per iteration and card; the card keeps its place on the board and the iteration only lists it. The cards of an iteration keep the order of their records.
A record of this entity needs records of other entities in the package: Cards; Iterations.
Files in the package
List every file of this entity in resource_files of the manifest, with "resource": "iteration_cards". An entity can have any number of files. See Bundle format.
[
  {
    "resource": "iteration_cards",
    "path": "resources/iteration_cards.json"
  }
]
Fields
FieldTypeRequiredDescription
external_idstring (ExternalId)YesYour 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.

card_refRef<cards>

refers to Cards

YesThe card that belongs to the iteration. Give the external_id of a cards record.
iteration_refRef<iterations>

refers to Iterations

YesThe iteration. Give the external_id of a iterations record.
added_by_refRef<users>?

refers to Users

NoThe user who put the card into the iteration. Give the external_id of a users record.
created_atTimestampNoWhen the record was created, with a time zone, for example 2026-01-12T09:30:00Z.

Constraints: RFC 3339 with a time zone.

Default: source.exported_at of the manifest

References

Refers to

Show on the entity map
Example
A record of this entity:
{
  "external_id": "ic-1-mrr",
  "iteration_ref": "it-1",
  "card_ref": "k-mrr",
  "added_by_ref": "u-ava"
}
Rules
  • The combination of iteration_ref, card_ref must be unique.
Related entities
Cards, Iterations, Users
Check after the import
After the import, the records of this entity can be checked on Iterations › Retrieve cards in iteration.
JSON Schema
iteration_cards.json
logo
Kaiten
If you have any questions or need help with integration feel free to write us at support@kaiten.ru