Sign in
TrackerItem

Read tracker items for use as a test-generation specification

The readable content of each item: a fixed set of fields chosen by the item's category, converted to plain text, with test case steps parsed into action and expected pairs. The integration must belong to this workspace and be enabled, and each item must lie in its configured project. Every item reports readable and a reason, so one bad item does not fail the request.

post/issueTrackers/workspaces/{workspace_id}/items:content

Path parameters

workspace_idstring required

Request body

workspace_integration_idstring required

The integration whose project holds these items. Item ids are unique only per organization, so the caller must say which; it is validated against the workspace.

issue_keysstring[] required

Canonical keys, at most 5 -- each costs upstream calls and prompt budget

Response

One entry per requested key, in request order

Example response

{
  "items": [
    {
      "issue_key": "123",
      "display_key": "AB#123"
    }
  ]
}

Changes

Changed in 1 of the 32 revisions of this API.1