> ## Documentation Index
> Fetch the complete documentation index at: https://docs.parable.work/llms.txt
> Use this file to discover all available pages before exploring further.

# Zephyr Cloud REST API

> Zephyr Cloud is SmartBear's test management solution for Jira Cloud. The v2 REST API provides access to test cases, test cycles, test executions, folders, environments, statuses, and priorities.

Zephyr Cloud is SmartBear's test management solution for Jira Cloud. The v2 REST API provides access to test cases, test cycles, test executions, folders, environments, statuses, and priorities.

<Tabs>
  <Tab title="Overview">
    Connect Parable to Zephyr Cloud using a single API access token. Parable ingests test cases, test cycles, execution results, and step-level data across all Jira projects accessible to the token.

    #### Test execution data

    Test cycles, executions, and step-level results

    #### Test definition data

    Test cases and their step definitions

    ## Data streams

    This Provider Plugin defines 14 data streams.

    | Stream                | Description                                                                                                                                                                                                                                                                                                                                           | Sync |
    | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- |
    | `testcases`           | Extracts all test cases across all Jira projects accessible to the token. Uses the cursor-based nextgen endpoint for reliable large-dataset pagination.                                                                                                                                                                                               | full |
    | `testcycles`          | Extracts all test cycles across all Jira projects accessible to the token.                                                                                                                                                                                                                                                                            | full |
    | `testexecutions`      | Extracts all test executions across all Jira projects. Uses the cursor-based nextgen endpoint for reliable large-dataset pagination.                                                                                                                                                                                                                  | full |
    | `testcase_steps`      | Extracts test step definitions for each test case. Requires a parent testCaseKey -- fanout from testcases tap.                                                                                                                                                                                                                                        | full |
    | `testexecution_steps` | Extracts test step execution results for each test execution. Requires a parent testExecutionKey -- fanout from testexecutions tap.                                                                                                                                                                                                                   | full |
    | `folders`             | Extracts all folders used to organize test cases, test cycles, and test plans across all projects.                                                                                                                                                                                                                                                    | full |
    | `projects`            | Extracts all Jira projects that have Zephyr Cloud enabled.                                                                                                                                                                                                                                                                                            | full |
    | `environments`        | Extracts all test environments defined across all projects.                                                                                                                                                                                                                                                                                           | full |
    | `testplans`           | Extracts all test plans across all projects.                                                                                                                                                                                                                                                                                                          | full |
    | `statuses`            | Extracts all test result and test case statuses defined across all projects.                                                                                                                                                                                                                                                                          | full |
    | `priorities`          | Extracts all test case priority levels defined across all projects.                                                                                                                                                                                                                                                                                   | full |
    | `testcase_versions`   | Extracts version history snapshots for each test case. Requires a parent testCaseKey -- fanout from testcases tap.                                                                                                                                                                                                                                    | full |
    | `testcase_links`      | Extracts Jira issue links associated with each test case. Requires a parent testCaseKey -- fanout from testcases tap. Shares GET /testcases/{testCaseKey}/links with testcase\_weblinks; ingestion fetches that endpoint once per tap today (2x HTTP per test case). Follow-up: consolidate to one tap and split issues/webLinks in bronze or silver. | full |
    | `testcase_weblinks`   | Extracts external web links associated with each test case. Requires a parent testCaseKey -- fanout from testcases tap. Shares GET /testcases/{testCaseKey}/links with testcase\_links; ingestion fetches that endpoint once per tap today (2x HTTP per test case). Follow-up: consolidate to one tap and split issues/webLinks in bronze or silver.  | full |
  </Tab>

  <Tab title="Setup Guide">
    ### Zephyr Cloud

    #### What You'll Need

    | Credential           | What it is                                                                    |
    | -------------------- | ----------------------------------------------------------------------------- |
    | **API Access Token** | A token generated from your Jira Cloud profile under Zephyr API Access Tokens |

    * A **Jira Cloud account** with **Zephyr Cloud** (or Zephyr Cloud) installed.
    * Your account must have permission to access test data in at least one Jira project.

    #### Step 1: Open Zephyr API Access Tokens

    1. Sign in to Jira Cloud.
    2. Click your **profile icon** in the top-right corner.
    3. Select **Zephyr API Access Tokens** from the dropdown menu.

    > **Tip:** You can also navigate directly to your Jira Cloud instance and look for "Zephyr API Access Tokens" in your profile menu.

    #### Step 2: Create a new access token

    1. Click **Create access token**.
    2. Give the token a descriptive name (e.g. "Parable integration").
    3. Copy the generated token immediately.

    > **Warning:** **Copy your {tokenName} now!**
    >
    > This is the only time it will be displayed. Store it in a secure password manager before closing this page.

    > **Warning:** The token is shown only once at creation time. If you navigate away without copying it, you must create a new token.

    #### Step 3: Connect in Parable

    1. In Parable, open **Platform → Providers** and choose the Provider to add.
    2. Select **Zephyr Cloud**.
    3. Paste your **API Access Token**.
    4. Click **Save & verify**.

    > **Success:** **Success!** If you received a `200 OK` response with valid data, your credentials are configured correctly. You can now configure this Provider in Parable.

    > **Tip:** **Rate Limits:** {platform} enforces rate limits of **{limit}**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
  </Tab>

  <Tab title="Permissions">
    <AccordionGroup>
      <Accordion id="provider-permission-tap-zephyrcloud-environments-7602eb27e716" title="Environments" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `environments`

        Environments contain all test environments defined across all projects.

        * **Enables:** interpret test executions against their configured test environment.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/environments` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-environments-description-c5d683a3aea9" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `environments.description`

            Description records description of the environment. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each environment record.
            * **Interpretation:** The provider supplies `description` at environment granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-environments-id-01d86a70fd42" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `environments.id`

            ID is the unique internal identifier of the environment. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same environment source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per environment record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-environments-name-333265d80d71" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `environments.name`

            Name records display name of the environment (e.g., Production, Staging). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each environment record.
            * **Interpretation:** The provider supplies `name` at environment granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-environments-project-ff714cfbd32e" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `environments.project`

            Project records Jira project reference; Cloud v2 returns a nested `{id, self}` object. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a environment record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each environment record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-environments-project-id-cf1f10f7cc2e" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `environments.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match environment records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `Environment`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-environments-project-self-1f155343fc30" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `environments.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a environment record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each environment record. Availability still follows the provider's permissions and retention.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-folders-f2cf85855b7b" title="Folders" icon="file-code" iconType="sharp-duotone-solid">
        Developer identifier: `folders`

        Folders contain all folders used to organize test cases, test cycles, and test plans across all projects.

        * **Enables:** reconstruct folders used to organize test cases, cycles, and plans.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/folders` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-folders-foldertype-aff78d6d844d" title="Folder Type" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `folders.folderType`

            Folder Type states type of objects in this folder: `TEST_CASE`, `TEST_CYCLE`, or `TEST_PLAN`. It preserves the provider's current classification of this record.

            * **Enables:** separate folder records by the exact provider-reported folder type value when describing their recorded state.
            * **Interpretation:** The provider supplies `folderType` per folder record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-folders-id-7c0209fa9999" title="ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `folders.id`

            ID is the unique internal identifier of the folder. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same folder source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per folder record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-folders-name-dedd19dd586f" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `folders.name`

            Name records display name of the folder. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each folder record.
            * **Interpretation:** The provider supplies `name` at folder granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-folders-parentid-4c2afd4dd23a" title="Parent ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `folders.parentId`

            Parent ID reports the numeric ID of the parent folder; null if root-level. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match folder records to provider records that carry the same parent ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `parentId` as a record-level identifier on `Folder`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-folders-project-8f1adfc18f21" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `folders.project`

            Project records Jira project reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a folder record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each folder record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-folders-project-id-5f0a74540b03" title="ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `folders.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match folder records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `Folder`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-folders-project-self-18628bdef827" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `folders.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a folder record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each folder record. Availability still follows the provider's permissions and retention.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-priorities-89bb1cf94140" title="Priorities" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `priorities`

        Priorities contain all test case priority levels defined across all projects.

        * **Enables:** interpret test-case priority identifiers using provider-defined labels.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/priorities` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-priorities-color-5a59a39dbf97" title="Color" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.color`

            Color records color code associated with the priority for UI display. It preserves the provider's visual treatment for the represented object.

            * **Enables:** reproduce or compare the provider-supplied color for the represented design or board object.
            * **Interpretation:** The provider supplies `color` in its own color, opacity, stroke, emoji, or style vocabulary for the represented object.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-default-6fe3adb6eb11" title="Default" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.default`

            Default indicates whether this is the default priority. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select priority records for which the provider reports default as true or false.
            * **Interpretation:** The provider supplies `default` as a boolean per priority record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-description-93a7a36390a5" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.description`

            Description records description of the priority level. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each priority record.
            * **Interpretation:** The provider supplies `description` at priority granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-id-e0cb731f334f" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.id`

            ID is the unique internal identifier of the priority. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same priority source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per priority record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-name-aa3c06649ffd" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.name`

            Name records display name of the priority (e.g., High, Medium, Low). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each priority record.
            * **Interpretation:** The provider supplies `name` at priority granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-project-b408f967b295" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.project`

            Project records Jira project reference; Cloud v2 returns a nested `{id, self}` object. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a priority record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each priority record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-project-id-d8e941f0d21c" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match priority records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `Priority`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-priorities-project-self-ae3296a17289" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `priorities.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a priority record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each priority record. Availability still follows the provider's permissions and retention.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-projects-f2e59edce46e" title="Projects" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `projects`

        Projects contain all Jira projects that have Zephyr Cloud enabled.

        * **Enables:** enumerate Jira projects for which Zephyr Cloud returns a project record.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/projects` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-projects-description-f54eaf5d60c3" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.description`

            Description records description of the project. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each project record.
            * **Interpretation:** The provider supplies `description` at project granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-projects-enabled-1d9a5727dd92" title="Enabled" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `projects.enabled`

            Enabled indicates whether Zephyr Cloud is enabled for this project. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports enabled as true or false.
            * **Interpretation:** The provider supplies `enabled` as a boolean per project record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-projects-id-476c7f7f4df8" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.id`

            ID is the unique internal identifier of the project. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same project source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per project record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-projects-jiraprojectid-58786b903948" title="Jira Project ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.jiraProjectId`

            Jira Project ID reports the numeric Jira project ID, the matching key to Jira project data. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match project records to provider records that carry the same jira project ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `jiraProjectId` as a record-level identifier on `Project`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-projects-key-451ae5fbbc64" title="Key" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.key`

            Key identifies Jira project key (e.g., PROJ). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match project records to provider records that carry the same key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `key` as a record-level identifier on `Project`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-projects-name-9f6f8e984ce3" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.name`

            Name records name of the project. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each project record.
            * **Interpretation:** The provider supplies `name` at project granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-statuses-c1d8c71bf62d" title="Statuses" icon="circle-check" iconType="sharp-duotone-solid">
        Developer identifier: `statuses`

        Statuses contain all test result and test case statuses defined across all projects.

        * **Enables:** interpret test case and execution status identifiers using provider-defined labels.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/statuses` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-statuses-color-b8292188dc76" title="Color" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.color`

            Color records color code associated with the status for UI display. It preserves the provider's visual treatment for the represented object.

            * **Enables:** reproduce or compare the provider-supplied color for the represented design or board object.
            * **Interpretation:** The provider supplies `color` in its own color, opacity, stroke, emoji, or style vocabulary for the represented object.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-default-39b3c766076b" title="Default" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.default`

            Default indicates whether this is the default status for its type. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select status records for which the provider reports default as true or false.
            * **Interpretation:** The provider supplies `default` as a boolean per status record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-description-fc77aab3b7bf" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.description`

            Description records description of the status. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each status record.
            * **Interpretation:** The provider supplies `description` at status granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-id-2c452a622c3e" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.id`

            ID is the unique internal identifier of the status. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same status source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per status record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-name-f91a368d69f3" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.name`

            Name records display name of the status (e.g., Pass, Fail, Draft). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each status record.
            * **Interpretation:** The provider supplies `name` at status granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-project-8577ae9c2f4e" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.project`

            Project records Jira project reference; Cloud v2 returns a nested `{id, self}` object. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a status record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each status record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-project-id-4b3afddafa51" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match status records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `Status`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-project-self-9aa0ecbe8594" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a status record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each status record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-statuses-type-c9981b7341d1" title="Type" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `statuses.type`

            Type states type of object this status applies to: `TEST_CASE`, `TEST_CYCLE`, or `TEST_EXECUTION`. It preserves the provider's current classification of this record.

            * **Enables:** separate status records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per status record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testcase-links-50306a28fab3" title="Testcase Links" icon="link" iconType="sharp-duotone-solid">
        Developer identifier: `testcase_links`

        Testcase Links contain Jira issue links associated with each test case. Requires a parent `testCaseKey` -- fanout from testcases tap. Shares GET /testcases/`{`testCaseKey`}`/links with `testcase_weblinks`; ingestion fetches that endpoint once per tap today (2x HTTP per test case). Follow-up: consolidate to one tap and split issues/`webLinks` in bronze or silver.

        * **Enables:** associate test cases with the Jira issue links returned by Zephyr.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testcases/{testCaseKey}/links` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testcase-links-id-83c2b67d4217" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_links.id`

            ID is the unique internal identifier of the link. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test case link source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test case link record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-links-issueid-cd1d5c211c31" title="Issue ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_links.issueId`

            Issue ID identifies Jira issue ID linked to this test case. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcase link records to provider records that carry the same issue ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `issueId` as a record-level identifier on `TestCaseLink`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-links-testcasekey-b646e5397cdb" title="Test Case Key" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_links.testCaseKey`

            Test Case Key identifies parent key injected by the ingestor from the testcases to `testcase_links` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcase link records to provider records that carry the same test case key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `testCaseKey` as a record-level identifier on `TestCaseLink`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-links-type-7fab96972a4e" title="Type" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_links.type`

            Type states link type: COVERAGE, BLOCKS, or RELATED. It preserves the provider's current classification of this record.

            * **Enables:** separate testcase link records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per test case link record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testcase-steps-f30642f34ea7" title="Testcase Steps" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testcase_steps`

        Testcase Steps contain test step definitions for each test case. Requires a parent `testCaseKey` -- fanout from testcases tap.

        * **Enables:** inspect ordered test-step definitions for each parent test case.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testcases/{testCaseKey}/teststeps` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-id-857aaa45da2b" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.id`

            ID identifies synthetic primary key composed from the parent `testCaseKey` and the step index; Cloud v2 step envelopes carry no globally-unique id, so this key keeps dedup unique across parents. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test case step source row before constructing its represented state.
            * **Interpretation:** Parable generates `id` at one value per test case step record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-index-702fe7bc0e35" title="Index" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.index`

            Index reports zero-based ordinal position of this step within its test case. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify testcase step records using the provider-defined index value.
            * **Interpretation:** The provider supplies `index` at test case step granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-inline-ce6cdbe94222" title="Inline" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.inline`

            Inline records inline step definition; Cloud v2 nests step content under this envelope. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact inline value attached to each test case step record.
            * **Interpretation:** The provider supplies `inline` at test case step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-inline-customfields-4fc43cb71b32" title="Custom Fields" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.inline.customFields`

            Custom Fields records custom field values as a key-value map. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret custom fields according to the provider and Workspace configuration that produced each testcase step record.
            * **Interpretation:** Keys and value shapes within `customFields` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-inline-description-760bd419d003" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.inline.description`

            Description records step description / action to perform. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each test case step record.
            * **Interpretation:** The provider supplies `description` at test case step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-inline-expectedresult-9111c7694154" title="Expected Result" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.inline.expectedResult`

            Expected Result records expected result for this step. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact expected result value attached to each test case step record.
            * **Interpretation:** The provider supplies `expectedResult` at test case step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-inline-testdata-eb0ab2f96d82" title="Test Data" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.inline.testData`

            Test Data records test data associated with this step. It keeps this specific test data attribute attached to the test case step record.

            * **Enables:** compare the provider-defined test data values across testcase step records using the meaning stated in the field description.
            * **Interpretation:** The provider supplies `testData` once per test case step record as `string`. Missing and explicit values remain distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-steps-testcasekey-258f1e98f6de" title="Test Case Key" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_steps.testCaseKey`

            Test Case Key identifies parent key injected by the ingestor from the testcases to `testcase_steps` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcase step records to provider records that carry the same test case key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `testCaseKey` as a record-level identifier on `TestCaseStep`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testcase-versions-01d84f6754f6" title="Testcase Versions" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testcase_versions`

        Testcase Versions contain version history snapshots for each test case. Requires a parent `testCaseKey` -- fanout from testcases tap.

        * **Enables:** compare the provider-returned version snapshots of each test case.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testcases/{testCaseKey}/versions` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testcase-versions-createdon-455519bb52c1" title="Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_versions.createdOn`

            Created On records ISO 8601 timestamp when this version was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testcase version records on a timeline by created on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdOn` per test case version record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-versions-id-37c667cd5280" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_versions.id`

            ID is the unique internal identifier of the test case version. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test case version source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test case version record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-versions-self-59536bff6097" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_versions.self`

            Self records self URL of the version resource. The versions endpoint returns id-only link objects, not full snapshots. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case version record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case version record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-versions-testcasekey-5d0a2f83e7e3" title="Test Case Key" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_versions.testCaseKey`

            Test Case Key identifies parent key injected by the ingestor from the testcases to `testcase_versions` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcase version records to provider records that carry the same test case key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `testCaseKey` as a record-level identifier on `TestCaseVersion`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testcase-weblinks-24ea2c43baa5" title="Testcase Weblinks" icon="link" iconType="sharp-duotone-solid">
        Developer identifier: `testcase_weblinks`

        Testcase Weblinks contain external web links associated with each test case. Requires a parent `testCaseKey` -- fanout from testcases tap. Shares GET /testcases/`{`testCaseKey`}`/links with `testcase_links`; ingestion fetches that endpoint once per tap today (2x HTTP per test case). Follow-up: consolidate to one tap and split issues/`webLinks` in bronze or silver.

        * **Enables:** retain the external web links attached to each test case.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testcases/{testCaseKey}/links` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testcase-weblinks-description-d07123a983f5" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_weblinks.description`

            Description records display description of the web link. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each test case web link record.
            * **Interpretation:** The provider supplies `description` at test case web link granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-weblinks-id-495e0bf42dc0" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_weblinks.id`

            ID is the unique internal identifier of the web link. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test case web link source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test case web link record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-weblinks-testcasekey-3a899eccc136" title="Test Case Key" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_weblinks.testCaseKey`

            Test Case Key identifies parent key injected by the ingestor from the testcases to `testcase_weblinks` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcase weblink records to provider records that carry the same test case key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `testCaseKey` as a record-level identifier on `TestCaseWebLink`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-weblinks-type-5743bd447654" title="Type" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_weblinks.type`

            Type states link type: COVERAGE, BLOCKS, or RELATED. It preserves the provider's current classification of this record.

            * **Enables:** separate testcase weblink records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per test case web link record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcase-weblinks-url-e371f44d4fdc" title="URL" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcase_weblinks.url`

            URL records URL of the linked resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by URL on a test case web link record.
            * **Interpretation:** The provider supplies `url` as a URL or resource locator on each test case web link record. Availability still follows the provider's permissions and retention.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testcases-65f4a4a25093" title="Testcases" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testcases`

        Testcases contain all test cases across all Jira projects accessible to the token. Uses the cursor-based nextgen endpoint for reliable large-dataset pagination.

        * **Enables:** review test-case definitions across token-visible Jira projects.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testcases/nextgen` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testcases-component-64dde763e39c" title="Component" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.component`

            Component records Jira component reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by component on a test case record.
            * **Interpretation:** The provider supplies `component` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-component-id-5190c51b4a0b" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.component.id`

            ID reports the numeric component ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-component-self-8cf372dbeded" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.component.self`

            Self records self URL of the component resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-createdbyid-cf3cb65d535c" title="Created By ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.createdById`

            Created By ID identifies atlassian account ID of the user who created the test case. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same created by ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `createdById` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-createdon-96af5c5c7d83" title="Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.createdOn`

            Created On records ISO 8601 timestamp when the test case was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place test case records on a timeline by created on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdOn` per test case record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-customfields-dd58baa5840c" title="Custom Fields" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.customFields`

            Custom Fields records custom field values as a key-value map. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret custom fields according to the provider and Workspace configuration that produced each test case record.
            * **Interpretation:** Keys and value shapes within `customFields` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-estimatedtime-f2b4cdf0ccf3" title="Estimated Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.estimatedTime`

            Estimated Time reports the planned test-case execution duration in milliseconds. It preserves the provider's effort estimate in an explicit unit.

            * **Enables:** compare planned execution time across test cases and schedule testing capacity.
            * **Interpretation:** The provider supplies `estimatedTime` as an integer duration in milliseconds, not an ordinal or sequence; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-folder-9bb16d6dee31" title="Folder" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.folder`

            Folder records containing folder reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by folder on a test case record.
            * **Interpretation:** The provider supplies `folder` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-folder-id-e3fc9d958ca6" title="ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.folder.id`

            ID reports the numeric folder ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-folder-self-d2e58e30ef05" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.folder.self`

            Self records self URL of the folder resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-id-9ad3136e543d" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.id`

            ID is the unique internal identifier of the test case. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test case source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test case record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-key-a60f7755b064" title="Key" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.key`

            Key identifies human-readable key (e.g. SA-T10). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `key` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-labels-7434fa901e2a" title="Labels" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.labels`

            Labels records labels applied to the test case. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** apply the provider-defined labels classifications to each test case record.
            * **Interpretation:** The provider returns `labels` as a list on `TestCase`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-name-540d8407db7b" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.name`

            Name records name/title of the test case. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each test case record.
            * **Interpretation:** The provider supplies `name` at test case granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-objective-2c06182a4fd5" title="Objective" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.objective`

            Objective records objective or purpose of the test case (may contain HTML). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact objective value attached to each test case record.
            * **Interpretation:** The provider supplies `objective` at test case granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-owner-167a896ec301" title="Owner" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.owner`

            Owner records test case owner reference; Cloud v2 returns `{self, `accountId`}`. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the test case record to the provider-reported actor represented by owner.
            * **Interpretation:** The provider supplies `owner` as identity or attribution context on each test case record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-owner-accountid-81f13ec5e3be" title="Account ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.owner.accountId`

            Account ID identifies atlassian account ID of the owner. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `accountId` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-owner-self-6c342a2b11d2" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.owner.self`

            Self records self URL of the owner resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-precondition-d15cf8b558f2" title="Precondition" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.precondition`

            Precondition records preconditions required before executing this test case (may contain HTML). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact precondition value attached to each test case record.
            * **Interpretation:** The provider supplies `precondition` at test case granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-priority-9fa4638a35bc" title="Priority" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.priority`

            Priority states test case priority reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate test case records by the exact provider-reported priority value when describing their recorded state.
            * **Interpretation:** The provider supplies `priority` per test case record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-priority-id-738656081df4" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.priority.id`

            ID reports the numeric priority ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-priority-self-b46bee58dd68" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.priority.self`

            Self records self URL of the priority resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-project-fc620340f53b" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.project`

            Project records Jira project reference; Cloud v2 returns a nested `{id, self}` object. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a test case record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-project-id-370a1efb77d6" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-project-self-a5ec2535825c" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-status-14a199347024" title="Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.status`

            Status states test case status reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate test case records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per test case record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-status-id-57b2f97e6e2a" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.status.id`

            ID reports the numeric status ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match test case records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCase`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-status-self-0174f3d01bb1" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.status.self`

            Self records self URL of the status resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test case record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test case record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcases-updatedon-1ace28960f12" title="Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcases.updatedOn`

            Updated On records ISO 8601 timestamp when the test case was last updated. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place test case records on a timeline by updated on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updatedOn` per test case record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testcycles-30c69a6d5d3a" title="Testcycles" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testcycles`

        Testcycles contain all test cycles across all Jira projects accessible to the token.

        * **Enables:** organize test executions by their Zephyr test cycles.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testcycles` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testcycles-createdon-3d5145d2a77f" title="Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.createdOn`

            Created On records ISO 8601 timestamp when the test cycle was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testcycle records on a timeline by created on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdOn` per test cycle record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-customfields-9e498b9378b0" title="Custom Fields" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.customFields`

            Custom Fields records custom field values as a key-value map. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret custom fields according to the provider and Workspace configuration that produced each testcycle record.
            * **Interpretation:** Keys and value shapes within `customFields` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-description-dd0c7cf090e2" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.description`

            Description records description of the test cycle. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each test cycle record.
            * **Interpretation:** The provider supplies `description` at test cycle granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-folder-9620ba854e36" title="Folder" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.folder`

            Folder records containing folder reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by folder on a test cycle record.
            * **Interpretation:** The provider supplies `folder` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-folder-id-36bb4bfd0b53" title="ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.folder.id`

            ID reports the numeric folder ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcycle records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCycle`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-folder-self-8087bdd937d6" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.folder.self`

            Self records self URL of the folder resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test cycle record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-id-721fd613de20" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.id`

            ID is the unique internal identifier of the test cycle. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test cycle source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test cycle record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-jiraprojectversion-ce836d9f1e71" title="Jira Project Version" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.jiraProjectVersion`

            Jira Project Version records Jira fix-version reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by jira project version on a test cycle record.
            * **Interpretation:** The provider supplies `jiraProjectVersion` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-jiraprojectversion-id-b26aacedf4e2" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.jiraProjectVersion.id`

            ID reports the numeric Jira fix-version ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcycle records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCycle`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-jiraprojectversion-self-bddc85d3ab5f" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.jiraProjectVersion.self`

            Self records self URL of the Jira fix-version resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test cycle record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-key-e8f8070f475f" title="Key" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.key`

            Key identifies human-readable key (e.g. SA-R40). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcycle records to provider records that carry the same key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `key` as a record-level identifier on `TestCycle`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-name-46deed0d4940" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.name`

            Name records name of the test cycle. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each test cycle record.
            * **Interpretation:** The provider supplies `name` at test cycle granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-owner-5abd0d38d0eb" title="Owner" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.owner`

            Owner records test cycle owner reference (`{self, `accountId`}`). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the test cycle record to the provider-reported actor represented by owner.
            * **Interpretation:** The provider supplies `owner` as identity or attribution context on each test cycle record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-owner-accountid-d09f362952f7" title="Account ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.owner.accountId`

            Account ID identifies atlassian account ID of the owner. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcycle records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `accountId` as a record-level identifier on `TestCycle`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-owner-self-e629053ada0d" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.owner.self`

            Self records self URL of the owner resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test cycle record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-plannedenddate-5420b4ac1d3c" title="Planned End Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.plannedEndDate`

            Planned End Date records planned end date (ISO 8601). It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testcycle records on a timeline by planned end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `plannedEndDate` per test cycle record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-plannedstartdate-e2167a4a651a" title="Planned Start Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.plannedStartDate`

            Planned Start Date records planned start date (ISO 8601). It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testcycle records on a timeline by planned start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `plannedStartDate` per test cycle record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-project-e21745e250ca" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.project`

            Project records Jira project reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a test cycle record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-project-id-175b942a8f0a" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcycle records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCycle`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-project-self-bc95e1b0ee8b" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test cycle record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-status-2b827e556e51" title="Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.status`

            Status states test cycle status reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate testcycle records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per test cycle record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-status-id-9c87919c2b79" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.status.id`

            ID reports the numeric status ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testcycle records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestCycle`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-status-self-5602fb1a4a07" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.status.self`

            Self records self URL of the status resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test cycle record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test cycle record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testcycles-updatedon-cfef473070e3" title="Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testcycles.updatedOn`

            Updated On records ISO 8601 timestamp when the test cycle was last updated. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testcycle records on a timeline by updated on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updatedOn` per test cycle record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testexecution-steps-1452a1b21d8d" title="Testexecution Steps" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testexecution_steps`

        Testexecution Steps contain test step execution results for each test execution. Requires a parent `testExecutionKey` -- fanout from testexecutions tap.

        * **Enables:** compare expected and actual step results for each parent test execution.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testexecutions/{testExecutionKey}/teststeps` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-actualresult-7faf5162fa82" title="Actual Result" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.actualResult`

            Actual Result records actual result recorded by the tester. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact actual result value attached to each test execution step record.
            * **Interpretation:** The provider supplies `actualResult` at test execution step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-id-81528a37e754" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.id`

            ID identifies synthetic primary key composed from the parent `testExecutionKey` and the step index; Cloud v2 step envelopes carry no globally-unique id, so this key keeps dedup unique across parents. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test execution step source row before constructing its represented state.
            * **Interpretation:** Parable generates `id` at one value per test execution step record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-index-a81dec03c84d" title="Index" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.index`

            Index reports zero-based ordinal position of this step within its execution. It preserves the stated measure at this record's granularity.

            * **Enables:** order or classify testexecution step records using the provider-defined index value.
            * **Interpretation:** The provider supplies `index` at test execution step granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-inline-836f70878913" title="Inline" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.inline`

            Inline records inline step definition; Cloud v2 nests step content under this envelope. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact inline value attached to each test execution step record.
            * **Interpretation:** The provider supplies `inline` at test execution step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-inline-descripti-d1439f842095" title="Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.inline.description`

            Description records step description / action. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact description value attached to each test execution step record.
            * **Interpretation:** The provider supplies `description` at test execution step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-inline-expectedr-cd7479cac91d" title="Expected Result" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.inline.expectedResult`

            Expected Result records expected result for this step. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact expected result value attached to each test execution step record.
            * **Interpretation:** The provider supplies `expectedResult` at test execution step granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-inline-testdata-e27c3c2a3e2b" title="Test Data" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.inline.testData`

            Test Data records test data for this step. It keeps this specific test data attribute attached to the test execution step record.

            * **Enables:** compare the provider-defined test data values across testexecution step records using the meaning stated in the field description.
            * **Interpretation:** The provider supplies `testData` once per test execution step record as `string`. Missing and explicit values remain distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-status-efd981320a08" title="Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.status`

            Status states step result status reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate testexecution step records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per test execution step record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-status-id-2f3929dfc4fa" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.status.id`

            ID reports the numeric status ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution step records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecutionStep`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-status-self-f61a8b989f11" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.status.self`

            Self records self URL of the status resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution step record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution step record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecution-steps-testexecutionkey-d6ad0fde4c4c" title="Test Execution Key" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testexecution_steps.testExecutionKey`

            Test Execution Key identifies parent key injected by the ingestor from the testexecutions to `testexecution_steps` traversal `parentContextFields`. Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution step records to provider records that carry the same test execution key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `testExecutionKey` as a record-level identifier on `TestExecutionStep`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testexecutions-ad305026220c" title="Testexecutions" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testexecutions`

        Testexecutions contain all test executions across all Jira projects. Uses the cursor-based nextgen endpoint for reliable large-dataset pagination.

        * **Enables:** measure recorded test outcomes by case, cycle, environment, and execution time.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testexecutions/nextgen` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-actualenddate-87a3cc57f3fe" title="Actual End Date" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.actualEndDate`

            Actual End Date records ISO 8601 timestamp when the execution completed. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testexecution records on a timeline by actual end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `actualEndDate` per test execution record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-assignedto-b75cbcea6f93" title="Assigned To" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.assignedTo`

            Assigned To records user assigned to execute the test (`{self, `accountId`}`). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the test execution record to the provider-reported person or account represented by assigned to.
            * **Interpretation:** The provider supplies `assignedTo` as identity or attribution context on each test execution record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-assignedto-accountid-d401c033b2d7" title="Account ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.assignedTo.accountId`

            Account ID identifies atlassian account ID of the assignee. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `accountId` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-assignedto-self-d609c6e3e2e7" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.assignedTo.self`

            Self records self URL of the assignee resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-automated-442d45eb1734" title="Automated" icon="diagram-project" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.automated`

            Automated indicates whether this execution was automated. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select testexecution records for which the provider reports automated as true or false.
            * **Interpretation:** The provider supplies `automated` as a boolean per test execution record; false and missing are distinct when the field is optional.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-comment-ec2eda23986b" title="Comment" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.comment`

            Comment records comment added to this execution. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact comment value attached to each test execution record.
            * **Interpretation:** The provider supplies `comment` at test execution granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-createdon-c06a407c5253" title="Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.createdOn`

            Created On records ISO 8601 timestamp when the execution record was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testexecution records on a timeline by created on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdOn` per test execution record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-customfields-578e5feb4f3b" title="Custom Fields" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.customFields`

            Custom Fields records custom field values as a key-value map. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret custom fields according to the provider and Workspace configuration that produced each testexecution record.
            * **Interpretation:** Keys and value shapes within `customFields` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-environment-b59f9fee21a6" title="Environment" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.environment`

            Environment states execution environment reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate testexecution records by the exact provider-reported environment value when describing their recorded state.
            * **Interpretation:** The provider supplies `environment` per test execution record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-environment-id-2a7a010978f2" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.environment.id`

            ID reports the numeric environment ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-environment-self-7f7bbfdbbe25" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.environment.self`

            Self records self URL of the environment resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-estimatedtime-a85d37f9b68b" title="Estimated Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.estimatedTime`

            Estimated Time reports the planned test-execution duration in milliseconds. It preserves the expected effort attached to the execution.

            * **Enables:** compare planned duration with actual execution time and identify executions that exceed their estimate.
            * **Interpretation:** The provider supplies `estimatedTime` as an integer duration in milliseconds, not an ordinal or sequence; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-executedby-3273e412fef1" title="Executed By" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.executedBy`

            Executed By records user who executed the test (`{self, `accountId`}`). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the test execution record to the provider-reported person or account represented by executed by.
            * **Interpretation:** The provider supplies `executedBy` as identity or attribution context on each test execution record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-executedby-accountid-d76d16565315" title="Account ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.executedBy.accountId`

            Account ID identifies atlassian account ID of the executor. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `accountId` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-executedby-self-20b15b486811" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.executedBy.self`

            Self records self URL of the executor resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-executiontime-7056ca8add07" title="Execution Time" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.executionTime`

            Execution Time reports the actual test-execution duration in milliseconds. It preserves elapsed execution time in an explicit unit.

            * **Enables:** compare actual duration with the estimate and identify unusually slow test executions.
            * **Interpretation:** The provider supplies `executionTime` as an integer duration in milliseconds; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-id-0b5f99ee65fc" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.id`

            ID is the unique internal identifier of the test execution. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test execution source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test execution record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-jiraprojectversion-ec7cb19ba8b7" title="Jira Project Version" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.jiraProjectVersion`

            Jira Project Version records Jira fix-version reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by jira project version on a test execution record.
            * **Interpretation:** The provider supplies `jiraProjectVersion` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-jiraprojectversion-id-d879afcc7362" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.jiraProjectVersion.id`

            ID reports the numeric Jira fix-version ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-jiraprojectversion-se-6c04f686f248" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.jiraProjectVersion.self`

            Self records self URL of the Jira fix-version resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-key-e293e5a28903" title="Key" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.key`

            Key identifies human-readable key (e.g. SA-E10). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `key` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-project-9d20b72eb146" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.project`

            Project records Jira project reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a test execution record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-project-id-3c843c66b9da" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-project-self-bdfc5fb6b6cc" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-status-f6a861901778" title="Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.status`

            Status states execution status reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate testexecution records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per test execution record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-status-id-f016447d721b" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.status.id`

            ID reports the numeric status ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-status-self-00553465e1a1" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.status.self`

            Self records self URL of the status resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-testcase-10c831bcb3fe" title="Test Case" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.testCase`

            Test Case records executed test case reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by test case on a test execution record.
            * **Interpretation:** The provider supplies `testCase` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-testcase-id-afbf84af19a7" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.testCase.id`

            ID reports the numeric test case ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-testcase-self-254ba1b63200" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.testCase.self`

            Self records self URL of the test case resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-testcycle-e802c357c9f7" title="Test Cycle" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.testCycle`

            Test Cycle records parent test cycle reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by test cycle on a test execution record.
            * **Interpretation:** The provider supplies `testCycle` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-testcycle-id-b2654eba4ea8" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.testCycle.id`

            ID reports the numeric test cycle ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testexecution records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestExecution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-testcycle-self-affc56db2225" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.testCycle.self`

            Self records self URL of the test cycle resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test execution record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test execution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testexecutions-updatedon-652df7a409ef" title="Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testexecutions.updatedOn`

            Updated On records ISO 8601 timestamp when the execution record was last updated. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testexecution records on a timeline by updated on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updatedOn` per test execution record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-zephyrcloud-testplans-1fb9c5248636" title="Testplans" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `testplans`

        Testplans contain all test plans across all projects.

        * **Enables:** organize related test cycles under Zephyr test plans.
        * **Scope:** Reads the declared collection through `GET /{apiVersion}/testplans` as a full snapshot. Results contain only Zephyr records returned for Jira projects accessible to the configured API token.

        <AccordionGroup>
          <Accordion id="provider-permission-field-zephyrcloud-testplans-createdon-cdcf1058bcde" title="Created On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.createdOn`

            Created On records ISO 8601 timestamp when the test plan was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testplan records on a timeline by created on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `createdOn` per test plan record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-customfields-8aea052f7c18" title="Custom Fields" icon="chart-line" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.customFields`

            Custom Fields records project-defined custom fields on the test plan. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret custom fields according to the provider and Workspace configuration that produced each testplan record.
            * **Interpretation:** Keys and value shapes within `customFields` can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-folder-357c086d38d0" title="Folder" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.folder`

            Folder records folder reference (`{id, self}`). It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by folder on a test plan record.
            * **Interpretation:** The provider supplies `folder` as a URL or resource locator on each test plan record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-folder-id-1696a60ac123" title="ID" icon="file-code" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.folder.id`

            ID reports the numeric folder ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testplan records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestPlan`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-folder-self-79ac8fa62054" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.folder.self`

            Self records self URL of the folder resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test plan record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test plan record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-id-45682dff4868" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.id`

            ID is the unique internal identifier of the test plan. It supplies the declared record identity used when repeated ingestions represent the same source row.

            * **Enables:** recognize repeated ingestions of the same test plan source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per test plan record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-key-6be2fefbe258" title="Key" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.key`

            Key identifies human-readable key. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testplan records to provider records that carry the same key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `key` as a record-level identifier on `TestPlan`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-labels-98f2ff9234b7" title="Labels" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.labels`

            Labels records labels attached to the test plan. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** apply the provider-defined labels classifications to each test plan record.
            * **Interpretation:** The provider returns `labels` as a list on `TestPlan`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-name-d61ea751d573" title="Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.name`

            Name records name of the test plan. It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact name value attached to each test plan record.
            * **Interpretation:** The provider supplies `name` at test plan granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-objective-f0cc4e177e5d" title="Objective" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.objective`

            Objective records objective of the test plan (Cloud v2 field; not description). It keeps the exact text, label, or authored value needed to interpret the record.

            * **Enables:** inspect the exact objective value attached to each test plan record.
            * **Interpretation:** The provider supplies `objective` at test plan granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-owner-fa3703c258fc" title="Owner" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.owner`

            Owner records owner reference (`{`accountId`, self}`). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the test plan record to the provider-reported actor represented by owner.
            * **Interpretation:** The provider supplies `owner` as identity or attribution context on each test plan record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-owner-accountid-518c1bb1d251" title="Account ID" icon="people-group" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.owner.accountId`

            Account ID identifies atlassian account ID of the owner. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testplan records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `accountId` as a record-level identifier on `TestPlan`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-owner-self-0944a89d735f" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.owner.self`

            Self records self URL of the user resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test plan record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test plan record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-project-b7fa8334bda2" title="Project" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.project`

            Project records Jira project reference; Cloud v2 returns a nested `{id, self}` object. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by project on a test plan record.
            * **Interpretation:** The provider supplies `project` as a URL or resource locator on each test plan record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-project-id-391ddbfb3bf1" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.project.id`

            ID reports the numeric project ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testplan records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestPlan`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-project-self-f2796a99b046" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.project.self`

            Self records self URL of the project resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test plan record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test plan record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-status-d1a417aa40f7" title="Status" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.status`

            Status states test plan status reference (`{id, self}`). It preserves the provider's current classification of this record.

            * **Enables:** separate testplan records by the exact provider-reported status value when describing their recorded state.
            * **Interpretation:** The provider supplies `status` per test plan record using its own state vocabulary; unknown and missing values must remain distinct.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-status-id-206881bee93e" title="ID" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.status.id`

            ID reports the numeric status ID. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match testplan records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `TestPlan`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-status-self-dac0611fe334" title="Self" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.status.self`

            Self records self URL of the status resource. It retains the exact provider location for the referenced resource.

            * **Enables:** open or trace the exact provider resource referenced by self on a test plan record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each test plan record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-zephyrcloud-testplans-updatedon-f6d56ce1a850" title="Updated On" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `testplans.updatedOn`

            Updated On records ISO 8601 timestamp when the test plan was last updated. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place testplan records on a timeline by updated on and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updatedOn` per test plan record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    **Validation fails immediately after entering the token**

    * Confirm you copied the full token without leading or trailing whitespace.
    * The token may have been revoked. Return to the Zephyr API Access Tokens page and create a new one.
    * Ensure your Jira account has access to at least one project with Zephyr Cloud data.

    **Some projects show no data**

    * Zephyr access is scoped to Jira project permissions. The account that generated the token must have at least **Browse Projects** permission in every project you want to ingest.

    **Rate limit errors during initial sync**

    * Zephyr Cloud enforces rate limits per token. Parable automatically respects retry delays. A large initial sync across many projects may take longer than expected -- no action required.

    **`testcases` or `testcycles` tap returns empty results**

    * Confirm that test cases and cycles exist in your Jira projects. If no test data has been created in Zephyr Cloud, the taps will return no records.
  </Tab>
</Tabs>