> ## 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.

# Jira Cloud

> Sync issues, projects, and users from Jira Cloud

Sync issues, projects, and users from Jira Cloud.

<Tabs>
  <Tab title="Overview">
    ## Jira Cloud setup

    Parable lists one **Jira Cloud** Provider under Atlassian. In the connection wizard, use **Authentication method** to choose **Email + API Token** or **OAuth 2.0 Client Credentials (2LO)**.

    Both methods sync the same taps: projects, users, issues, and changelogs.

    ## Data streams

    This Provider Plugin defines 5 data streams.

    | Stream       | Description                                                   | Sync        |
    | ------------ | ------------------------------------------------------------- | ----------- |
    | `projects`   | Jira Cloud projects                                           | full        |
    | `users`      | Jira Cloud users                                              | full        |
    | `issues`     | Jira Cloud issues via enhanced JQL search                     | incremental |
    | `changelogs` | Issue change history                                          | full        |
    | `comments`   | Issue comments including author and updateAuthor user objects | full        |
  </Tab>

  <Tab title="Setup Guide">
    ### Jira

    #### What You'll Need

    | Credential          | What it is                                                          |
    | ------------------- | ------------------------------------------------------------------- |
    | **API Token**       | Generated from Atlassian account settings                           |
    | **Email Address**   | Your Atlassian account email                                        |
    | **Base URL**        | Your Jira instance URL (e.g., `https://your-company.atlassian.net`) |
    | **Domain**          | Your Atlassian domain (e.g., `your-company.atlassian.net`)          |
    | **Organization ID** | Your Atlassian organization ID                                      |

    #### Prerequisites

    * **Global permission**: Administer Jira
    * **Project permission**: Browse Projects
    * User emails visible to "Anyone" in Atlassian profile settings

    #### Setup

    1. Create an API token at [https://id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
    2. Find Organization ID in the Atlassian Admin Console URL
    3. Note your Jira site URL (`https://your-company.atlassian.net`)
    4. In Parable, select **Email + API Token**, enter credentials and connection settings, then **Save & test connection**

    #### Verify

    Basic auth against `https://your-company.atlassian.net/rest/api/3/myself`.

    #### What You'll Need

    | Credential        | What it is                                                                |
    | ----------------- | ------------------------------------------------------------------------- |
    | **Client ID**     | From the service account OAuth 2.0 credential in Atlassian Administration |
    | **Client Secret** | From the same OAuth 2.0 credential                                        |
    | **Cloud ID**      | Site identifier for api.atlassian.com gateway URLs                        |

    #### Prerequisites

    * Atlassian organization admin access
    * Service account with Jira product access on the target site
    * OAuth scopes: `read:jira-work`, `read:jira-user`
    * Jira permissions: Browse Projects, Browse users and groups

    #### Setup

    1. Create a service account in Atlassian Administration
    2. Create OAuth 2.0 credentials with scopes `read:jira-work` and `read:jira-user`
    3. Grant Browse Projects and Browse users and groups to the service account
    4. Find Cloud ID via admin console or `GET https://api.atlassian.com/oauth/token/accessible-resources`
    5. In Parable, select **OAuth 2.0 Client Credentials (2LO)**, enter Client ID, Client Secret, and Cloud ID, then **Save & test connection**

    #### Verify

    Token exchange requires `audience=api.atlassian.com`:

    ```bash theme={null}
    curl -X POST "https://auth.atlassian.com/oauth/token" \
      -H "Content-Type: application/x-www-form-urlencoded" \
      -d "grant_type=client_credentials" \
      -d "client_id=YOUR_CLIENT_ID" \
      -d "client_secret=YOUR_CLIENT_SECRET" \
      -d "audience=api.atlassian.com"
    ```

    Probe: `GET https://api.atlassian.com/ex/jira/CLOUD_ID/rest/api/3/project/search?maxResults=1`
  </Tab>

  <Tab title="Permissions">
    ### Jira

    | Endpoint                           | API Token permission    | OAuth scope    |
    | ---------------------------------- | ----------------------- | -------------- |
    | `/rest/api/3/project/search`       | Browse Projects         | read:jira-work |
    | `/rest/api/3/search/jql`           | Browse Projects         | read:jira-work |
    | `/rest/api/3/users/search`         | Browse users and groups | read:jira-user |
    | `/rest/api/3/issue/{id}/changelog` | Browse Projects         | read:jira-work |

    <AccordionGroup>
      <Accordion id="provider-permission-tap-jiracloud-changelogs-8c11a58bca5c" title="Changelogs" icon="badge-check" iconType="sharp-duotone-solid">
        Developer identifier: `changelogs`

        Changelogs contain issue change history.

        * **Enables:** reconstruct the field changes recorded for each parent issue.
        * **Scope:** Reads the declared collection through `GET /rest/api/3/issue/{id}/changelog` as a full snapshot. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-jiracloud-changelogs-author-56780a7f1ed1" title="Author" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author`

            Author captures the user who made the change. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira cloud changelog record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each jira cloud changelog record. In Jira Cloud, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-accountid-63a0037a596c" title="Account ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.accountId`

            Account ID captures the Atlassian account ID of the user. Unique, stable identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match changelog 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 `ChangelogAuthor`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-accounttype-b42f8afe010b" title="Account Type" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.accountType`

            Account Type captures the type of account (e.g., atlassian, app, customer). It preserves the provider's current classification of this record.

            * **Enables:** separate changelog records by the exact provider-reported account type value when describing their recorded state.
            * **Interpretation:** The provider supplies `accountType` per changelog author record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, account type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-active-3a736e88b67d" title="Active" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.active`

            Active indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select changelog records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per changelog author record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-avatarurls-0c8a5c998c93" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.avatarUrls`

            Avatar URLs records URLs for the user's avatar images in various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-avatarurls-16x16-969165162b7d" title="16x16" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.avatarUrls.16x16`

            16x16 records URL for the 16x16 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-avatarurls-24x24-fc1141417289" title="24x24" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.avatarUrls.24x24`

            24x24 records URL for the 24x24 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-avatarurls-32x32-7687cb081ad4" title="32x32" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.avatarUrls.32x32`

            32x32 records URL for the 32x32 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-avatarurls-48x48-71490e1dca12" title="48x48" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.avatarUrls.48x48`

            48x48 records URL for the 48x48 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-displayname-7d8e1184c3e3" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.displayName`

            Display Name captures the display name of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the changelog author record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each changelog author record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-emailaddress-52eccf09de9b" title="Email Address" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.emailAddress`

            Email Address captures the email address of the user, if visible. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the changelog author record to the provider-reported person or account represented by email address.
            * **Interpretation:** The provider supplies `emailAddress` as identity or attribution context on each changelog author record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-self-f59a0b7251de" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.self`

            Self records REST API URL for this 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 changelog author record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each changelog author record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-author-timezone-4471e1f8601a" title="Time Zone" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.author.timeZone`

            Time Zone captures the IANA time zone of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for changelogs using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per changelog author record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-created-1c7958dd4469" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.created`

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

            * **Enables:** place changelog records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per jira cloud changelog 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-jiracloud-changelogs-historymetadata-2782120f1b38" title="History Metadata" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata`

            History Metadata records metadata about the history record, including the activity that triggered the change. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested history metadata records contained by each jira cloud changelog record.
            * **Interpretation:** The provider returns `historyMetadata` as a nested object or reference on `JiraCloudChangelog`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-activitydes-4229d60eef16" title="Activity Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.activityDescription`

            Activity Description contains a description of the activity that triggered the change. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-activitydes-90d6479214f1" title="Activity Description Key" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.activityDescriptionKey`

            Activity Description Key captures the key of the activity description. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-dcb716193541" title="Actor" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor`

            Actor captures the user or system that performed the change. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the history metadata record to the provider-reported actor represented by actor.
            * **Interpretation:** The provider supplies `actor` as identity or attribution context on each history metadata record. In Jira Cloud, actor is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-avata-0dd3ca9928d1" title="Avatar URL" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor.avatarUrl`

            Avatar URL captures the URL of the participant's avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-displ-086946d3a15b" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor.displayName`

            Display Name captures the display name of the participant. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-displ-0c4683c7860b" title="Display Name Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor.displayNameKey`

            Display Name Key captures the key of the display name of the participant. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-id-cef22cb45558" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor.id`

            ID captures the ID of the participant. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match changelog 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 `HistoryMetadataParticipant`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-type-64ac650ae9f9" title="Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor.type`

            Type captures the type of the participant. It preserves the provider's current classification of this record.

            * **Enables:** separate changelog records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per history metadata participant record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-actor-url-147304458277" title="URL" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.actor.url`

            URL captures the URL of the participant. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-cause-f75ea7e4d136" title="Cause" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.cause`

            Cause captures the cause of the change (e.g., an automation rule or webhook). It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested cause object into its declared child fields for each history metadata record.
            * **Interpretation:** The provider returns `cause` as a nested object or reference on `HistoryMetadata`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-description-999281943463" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.description`

            Description contains a description of the history record. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-description-457efe3ccfb5" title="Description Key" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.descriptionKey`

            Description Key captures the description key of the history record. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-emaildescri-224b21b91afa" title="Email Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.emailDescription`

            Email Description captures the description of the email address associated with the history record. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-emaildescri-11b026819c78" title="Email Description Key" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.emailDescriptionKey`

            Email Description Key captures the description key of the email address. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-extradata-131dc264967e" title="Extra Data" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.extraData`

            Extra Data records additional arbitrary metadata associated with the history record. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret extra data according to the provider and Workspace configuration that produced each changelog record.
            * **Interpretation:** Keys and value shapes within `extraData` 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-jiracloud-changelogs-historymetadata-generator-4f2686c8e7f2" title="Generator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.generator`

            Generator captures the system or integration that generated the change. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested generator object into its declared child fields for each history metadata record.
            * **Interpretation:** The provider returns `generator` as a nested object or reference on `HistoryMetadata`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-historymetadata-type-44d30d0d7b24" title="Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.historyMetadata.type`

            Type captures the type of the history record. It preserves the provider's current classification of this record.

            * **Enables:** separate changelog records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per history metadata record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-id-ea6369a01dc4" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.id`

            ID is the unique ID of the changelog entry. Primary key for deduplication. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-issue-id-10ae0c3ac776" title="Issue ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.issue_id`

            Issue ID identifies parent issue's id, injected by the ingestion service from the issues tap's `parentContextFields`. Absent from the Jira changelog API response body itself. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-issue-key-aa4fa6374377" title="Issue Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.issue_key`

            Issue Key identifies parent issue's key (e.g. PROJ-42), injected by the ingestion service from the issues tap's `parentContextFields`. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-dd39f78a46da" title="Items" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items`

            Items records array of individual field changes within this changelog entry. Each item describes what field changed and the before/after values. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested items records contained by each jira cloud changelog record.
            * **Interpretation:** The provider returns `items` as a list on `JiraCloudChangelog`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-field-7a638ce97a31" title="Field" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.field`

            Field captures the human-readable name of the field that changed (e.g., 'status', 'assignee', 'priority'). It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-fieldid-82cadd83e17f" title="Field ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.fieldId`

            Field ID captures the ID of the field that changed. For system fields this is the field name; for custom fields it is the custom field ID (e.g., '`customfield_10010`'). It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-fieldtype-1b602dbcf23c" title="Fieldtype" icon="circle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.fieldtype`

            Fieldtype captures the type of the field that changed (e.g., 'jira', 'custom'). It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret fieldtype according to the provider and Workspace configuration that produced each changelog record.
            * **Interpretation:** Keys and value shapes within `fieldtype` 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-jiracloud-changelogs-items-from-6739d956034d" title="From" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.from`

            From captures the ID or machine-readable value of the field before the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded from with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `from` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-fromstring-d76e95a75986" title="From String" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.fromString`

            From String captures the human-readable display value of the field before the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded from string with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `fromString` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-tmpfromaccountid-e8799b3741df" title="Tmp From Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.tmpFromAccountId`

            Tmp From Account ID captures the account ID of the user in the 'from' value, when the field change involves a user (e.g., assignee changes). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-tmptoaccountid-4085f249ab9c" title="Tmp To Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.tmpToAccountId`

            Tmp To Account ID captures the account ID of the user in the 'to' value, when the field change involves a user (e.g., assignee changes). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-to-dfd057519cd6" title="To" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.to`

            To captures the ID or machine-readable value of the field after the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded to with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `to` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-changelogs-items-tostring-fc7c01dd0b26" title="To String" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `changelogs.items.toString`

            To String captures the human-readable display value of the field after the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded to string with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `toString` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-jiracloud-comments-696645faab93" title="Comments" icon="megaphone" iconType="sharp-duotone-solid">
        Developer identifier: `comments`

        Comments contain issue comments including author and `updateAuthor` user objects.

        * **Enables:** inspect issue-comment content with author, updater, visibility, and timestamp context.
        * **Scope:** Reads the declared collection through `GET /rest/api/3/issue/{id}/comment` as a full snapshot. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-jiracloud-comments-author-5caddc29338b" title="Author" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author`

            Author records user who authored the comment. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira cloud comment record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each jira cloud comment record. In Jira Cloud, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-accountid-1d4a10d1a92a" title="Account ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.accountId`

            Account ID captures the Atlassian account ID of the user. Unique, stable identifier. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match comment 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 `CommentAuthor`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-accounttype-8ea2519696a8" title="Account Type" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.accountType`

            Account Type captures the type of account (e.g., atlassian, app, customer). It preserves the provider's current classification of this record.

            * **Enables:** separate comment records by the exact provider-reported account type value when describing their recorded state.
            * **Interpretation:** The provider supplies `accountType` per comment author record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, account type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-active-9e4cc295888c" title="Active" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.active`

            Active indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select comment records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per comment author record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-avatarurls-e888ddf6af9e" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.avatarUrls`

            Avatar URLs records URLs for the user's avatar images in various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-comments-author-avatarurls-16x16-79a01927ef96" title="16x16" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.avatarUrls.16x16`

            16x16 records URL for the 16x16 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-comments-author-avatarurls-24x24-22ddc96db479" title="24x24" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.avatarUrls.24x24`

            24x24 records URL for the 24x24 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-comments-author-avatarurls-32x32-be6a2b216544" title="32x32" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.avatarUrls.32x32`

            32x32 records URL for the 32x32 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-comments-author-avatarurls-48x48-fd88e4957322" title="48x48" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.avatarUrls.48x48`

            48x48 records URL for the 48x48 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-comments-author-displayname-4c953ddd177b" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.displayName`

            Display Name captures the display name of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the comment author record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each comment author record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-emailaddress-3b74565106f8" title="Email Address" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.emailAddress`

            Email Address captures the email address of the user, if visible. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the comment author record to the provider-reported person or account represented by email address.
            * **Interpretation:** The provider supplies `emailAddress` as identity or attribution context on each comment author record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-self-39f3d52a6f05" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.self`

            Self records REST API URL for this 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 comment author record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each comment author record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-author-timezone-a78828059ce1" title="Time Zone" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `comments.author.timeZone`

            Time Zone captures the IANA time zone of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for comments using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per comment author record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-body-e1d47fb2a093" title="Body" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.body`

            Body records comment body in Atlassian Document Format (ADF). It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-comments-created-bdd02774ac05" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `comments.created`

            Created records the timestamp when the comment was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place comment records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per jira cloud comment 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-jiracloud-comments-id-d007205cad1a" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `comments.id`

            ID is the unique identifier for the comment. Primary key for deduplication. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-comments-issue-id-1c2e48c9a34a" title="Issue ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `comments.issue_id`

            Issue ID identifies parent issue's id, injected by the ingestion service from the issues tap's `parentContextFields`. Absent from the Jira comments API response body itself. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-comments-issue-key-fdbee8affc05" title="Issue Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `comments.issue_key`

            Issue Key identifies parent issue's key (e.g. PROJ-42), injected by the ingestion service from the issues tap's `parentContextFields`. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-comments-jsdpublic-99d71c39b373" title="Jsd Public" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `comments.jsdPublic`

            Jsd Public indicates whether the comment is visible to customers in Jira Service Desk. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select comment records for which the provider reports jsd public as true or false.
            * **Interpretation:** The provider supplies `jsdPublic` as a boolean per jira cloud comment record; false and missing are distinct when the field is optional. In Jira Cloud, jsd public is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-self-ca8abdd0834e" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.self`

            Self records REST API URL for this comment. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-comments-updateauthor-81ba26c56046" title="Update Author" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `comments.updateAuthor`

            Update Author records user who last updated the comment. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira cloud comment record to the provider-reported actor represented by update author.
            * **Interpretation:** The provider supplies `updateAuthor` as identity or attribution context on each jira cloud comment record. In Jira Cloud, update author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-updated-d1c897015979" title="Updated" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `comments.updated`

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

            * **Enables:** place comment records on a timeline by updated and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated` per jira cloud comment 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-jiracloud-comments-visibility-1c7dcd05d225" title="Visibility" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `comments.visibility`

            Visibility states visibility restriction for the comment. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported visibility attached to each jira cloud comment record.
            * **Interpretation:** The provider supplies `visibility` at jira cloud comment granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-visibility-identifier-5a74267e6ae1" title="Identifier" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `comments.visibility.identifier`

            Identifier is the identifier of the group or role. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-comments-visibility-type-6bc8322cbd95" title="Type" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.visibility.type`

            Type states type of visibility restriction (group or role). It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported type attached to each visibility object record.
            * **Interpretation:** The provider supplies `type` at visibility object granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, type is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-comments-visibility-value-8833f58e66a1" title="Value" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `comments.visibility.value`

            Value records name of the group or role. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded value with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `value` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-jiracloud-issues-334e27d18666" title="Issues" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `issues`

        Issues contain Jira Cloud issues via enhanced JQL search.

        * **Enables:** report issue content, state, priority, assignment, and project context without treating work state as individual performance.
        * **Scope:** Reads provider changes through `POST /rest/api/3/search/jql` using the declared incremental request boundary. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

        Provider-defined fields may also be returned for this data stream.

        <AccordionGroup>
          <Accordion id="provider-permission-field-jiracloud-issues-changelog-82db647b28d0" title="Changelog" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog`

            Changelog records changelog of field changes, present when `expand=changelog` is requested. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested changelog object into its declared child fields for each jira cloud issue record.
            * **Interpretation:** The provider returns `changelog` as a nested object or reference on `JiraCloudIssue`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-d0f8e7c72579" title="Histories" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories`

            Histories records list of changelog history entries. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested histories records contained by each changelog container record.
            * **Interpretation:** The provider returns `histories` as a list on `ChangelogContainer`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-e97bbf53b6ef" title="Author" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author`

            Author records user who made the changes. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the changelog history record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each changelog history record. In Jira Cloud, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-acco-e47db0e91670" title="Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.accountId`

            Account ID is the unique Atlassian account ID for the user. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `UserObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-acco-8e4034b09cbb" title="Account Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.accountType`

            Account Type states type of account (atlassian, app, customer). It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported account type value when describing their recorded state.
            * **Interpretation:** The provider supplies `accountType` per user object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, account type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-acti-aa1d3db3056c" title="Active" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.active`

            Active indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per user object record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-avat-59fa7e5bf8ac" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.avatarUrls`

            Avatar URLs records avatar image URLs at various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-avat-5ed9cd80ac07" title="16x16" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.avatarUrls.16x16`

            16x16 records 16x16 pixel avatar URL. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-avat-699f9dcafa3a" title="24x24" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.avatarUrls.24x24`

            24x24 records 24x24 pixel avatar URL. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-avat-f7cbd79a6665" title="32x32" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.avatarUrls.32x32`

            32x32 records 32x32 pixel avatar URL. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-avat-5f230039699d" title="48x48" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.avatarUrls.48x48`

            48x48 records 48x48 pixel avatar URL. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-disp-b8ef8f510139" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.displayName`

            Display Name records display name of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user object record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each user object record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-emai-db0d5138b302" title="Email Address" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.emailAddress`

            Email Address records email address of the user (if visible). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user object record to the provider-reported person or account represented by email address.
            * **Interpretation:** The provider supplies `emailAddress` as identity or attribution context on each user object record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-self-a11078b9b8ed" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.self`

            Self records REST API URL for this user. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-author-time-72885dcecb2f" title="Time Zone" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.timeZone`

            Time Zone records user's configured timezone. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for issues using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per user object record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-created-09ff439f94ff" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.created`

            Created records the timestamp when the changes were made. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per changelog history 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-jiracloud-issues-changelog-histories-id-1d0139e56f8d" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.id`

            ID is the unique identifier for this changelog entry. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `ChangelogHistory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-074a33e1d20e" title="Items" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items`

            Items records individual field changes in this changelog entry. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested items records contained by each changelog history record.
            * **Interpretation:** The provider returns `items` as a list on `ChangelogHistory`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-field-f265e1ea1736" title="Field" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.field`

            Field records name of the field that changed. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-field-eb1f81ea4157" title="Field ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.fieldId`

            Field ID is the ID of the field that changed. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-field-4a47794ef087" title="Fieldtype" icon="circle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.fieldtype`

            Fieldtype records type of the field (jira, custom). It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret fieldtype according to the provider and Workspace configuration that produced each issue record.
            * **Interpretation:** Keys and value shapes within `fieldtype` 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-jiracloud-issues-changelog-histories-items-from-ac3bfd5c23a4" title="From" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.from`

            From records previous value ID or key. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded from with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `from` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-froms-138968ca2325" title="From String" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.fromString`

            From String records previous value as a display string. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded from string with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `fromString` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-to-152e459a4fa8" title="To" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.to`

            To records new value ID or key. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded to with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `to` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-histories-items-tostr-b61d6ae42645" title="To String" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.toString`

            To String records new value as a display string. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded to string with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `toString` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-maxresults-726bb03b3a8c" title="Max Results" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.maxResults`

            Max Results reports maximum number of history entries returned. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported max results for each changelog container record.
            * **Interpretation:** The provider supplies `maxResults` at changelog container granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-startat-a2172cf51fa9" title="Start At" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.startAt`

            Start At identifies the pagination offset of the first changelog entry returned in the embedded page. It locates that page within the issue's complete history.

            * **Enables:** detect partial changelog pages and continue interpretation with `maxResults` and `total`.
            * **Interpretation:** The provider supplies `startAt` as a zero-based pagination offset, not a history count or business measure; zero denotes the first page.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-changelog-total-b08e70881ce5" title="Total" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.total`

            Total reports the total number of history entries. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total for each changelog container record.
            * **Interpretation:** The provider supplies `total` at changelog container granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-expand-0dde0eb37c14" title="Expand" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `issues.expand`

            Expand records comma-separated list of expanded sections in this response. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact expand when validating the configuration or technical definition of a jira cloud issue record.
            * **Interpretation:** The provider supplies `expand` as configuration or technical metadata on `JiraCloudIssue`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-e6d09d76155a" title="Fields" icon="ranking-star" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields`

            Fields records all fields of the issue. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret fields according to the provider and Workspace configuration that produced each issue record.
            * **Interpretation:** Keys and value shapes within `fields` 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-jiracloud-issues-fields-aggregateprogress-5abdd325c522" title="Aggregateprogress" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress`

            Aggregateprogress groups time spent, total estimated time, and completion percentage for the issue and its subtasks. It keeps the rollup separate from issue-only progress.

            * **Enables:** compare aggregate spent time with the estimate and identify issue trees that are incomplete or overrunning plan.
            * **Interpretation:** The provider supplies `aggregateprogress` as a nested progress object whose time fields are seconds and whose percent field uses a 0–100 scale; absence means no rollup was reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-aggregateprogress-percen-9e97402381b6" title="Percent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress.percent`

            Percent reports issue completion on a 0–100 percentage scale. It summarizes the relationship between time spent and the total estimate.

            * **Enables:** rank issue progress and distinguish not-started, partial, and complete work.
            * **Interpretation:** The provider supplies `percent` as an integer percentage per progress object; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-aggregateprogress-progre-29f670a68581" title="Progress" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress.progress`

            Progress reports time spent in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by progress across issue records.
            * **Interpretation:** The provider supplies `progress` per progress object record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-aggregateprogress-total-e62bb1a0d21e" title="Total" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress.total`

            Total reports the total estimated time in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by total across issue records.
            * **Interpretation:** The provider supplies `total` per progress object record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-aggregatetimeestimate-92cfe49321ff" title="Aggregatetimeestimate" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregatetimeestimate`

            Aggregatetimeestimate reports aggregate remaining estimate including subtasks, in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by aggregatetimeestimate across issue records.
            * **Interpretation:** The provider supplies `aggregatetimeestimate` per issue field record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-aggregatetimeoriginalest-656c035c3b66" title="Aggregatetimeoriginalestimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregatetimeoriginalestimate`

            Aggregatetimeoriginalestimate reports aggregate original estimate including subtasks, in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by aggregatetimeoriginalestimate across issue records.
            * **Interpretation:** The provider supplies `aggregatetimeoriginalestimate` per issue field record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-aggregatetimespent-97bf1224646e" title="Aggregatetimespent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregatetimespent`

            Aggregatetimespent reports aggregate time spent including subtasks, in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by aggregatetimespent across issue records.
            * **Interpretation:** The provider supplies `aggregatetimespent` per issue field record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-assignee-4dfc9df90f61" title="Assignee" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.assignee`

            Assignee records user assigned to this issue. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the issue field record to the provider-reported actor represented by assignee.
            * **Interpretation:** The provider supplies `assignee` as identity or attribution context on each issue field record. In Jira Cloud, assignee is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-07a1ebb72865" title="Attachment" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment`

            Attachment records file attachments on this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested attachment records contained by each issue field record.
            * **Interpretation:** The provider returns `attachment` as a list on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-author-b536ba0a4a19" title="Author" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.author`

            Author records user who uploaded the attachment. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the attachment object record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each attachment object record. In Jira Cloud, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-content-e2e5735ac731" title="Content" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.content`

            Content records URL to download the attachment content. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-created-495b34a43790" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.created`

            Created records the timestamp when the attachment was uploaded. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per attachment object 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-jiracloud-issues-fields-attachment-filename-8ab82d8b77ff" title="Filename" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.filename`

            Filename records name of the attached file. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-id-1d0356f76b57" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.id`

            ID is the unique identifier for the attachment. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `AttachmentObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-mimetype-1db487f96c4d" title="MIME Type" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.mimeType`

            MIME Type states MIME type of the attachment. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported MIME type value when describing their recorded state.
            * **Interpretation:** The provider supplies `mimeType` per attachment object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, MIME type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-self-c7e14ed90402" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.self`

            Self records REST API URL for this attachment. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-size-bc6470e2672c" title="Size" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.size`

            Size reports the attachment's file size in bytes. It preserves the payload footprint associated with the issue.

            * **Enables:** identify large attachments and estimate storage or transfer requirements.
            * **Interpretation:** The provider supplies `size` as an integer byte count per attachment; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-attachment-thumbnail-d2168184cc1a" title="Thumbnail" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.thumbnail`

            Thumbnail records URL for the attachment thumbnail. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-closedsprints-94ee9e76dbee" title="Closed Sprints" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints`

            Closed Sprints records closed sprints this issue was part of. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by closed sprints and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `closedSprints` per issue field 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-jiracloud-issues-fields-closedsprints-boardid-d16648bd39cb" title="Board ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.boardId`

            Board ID is the ID of the board this sprint belongs to. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-closedsprints-completeda-89ae3c220f85" title="Completion Date" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.completeDate`

            Completion Date records the date the sprint was completed. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by completion date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `completeDate` per sprint object 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-jiracloud-issues-fields-closedsprints-enddate-7948c786135b" title="End Date" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.endDate`

            End Date records end date of the sprint. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by end date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `endDate` per sprint object 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-jiracloud-issues-fields-closedsprints-goal-c5d23c6896cb" title="Goal" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.goal`

            Goal records goal of the sprint. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-closedsprints-id-052a1cdfa49a" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.id`

            ID is the unique identifier for the sprint. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `SprintObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-closedsprints-name-8b2334ea038c" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-closedsprints-self-99a7456f39aa" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.self`

            Self records REST API URL for this sprint. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-closedsprints-startdate-b4c08927d0ef" title="Start Date" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.startDate`

            Start Date records start date of the sprint. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per sprint object 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-jiracloud-issues-fields-closedsprints-state-192da4b1b5c7" title="State" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.state`

            State states current state of the sprint. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported state value when describing their recorded state.
            * **Interpretation:** The provider supplies `state` per sprint object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, state is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-14d4b47bbd86" title="Comment" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment`

            Comment records comments on this issue. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-661dc550513b" title="Comments" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments`

            Comments records list of comments on the issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested comments records contained by each comment container record.
            * **Interpretation:** The provider returns `comments` as a list on `CommentContainer`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-author-fc53a9d19ef2" title="Author" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.author`

            Author records user who authored the comment. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the comment object record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each comment object record. In Jira Cloud, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-body-7e9f33deac88" title="Body" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.body`

            Body records comment body in Atlassian Document Format (ADF). It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-created-efe625ab03dd" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.created`

            Created records the timestamp when the comment was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per comment object 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-jiracloud-issues-fields-comment-comments-id-849cf14fbb27" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.id`

            ID is the unique identifier for the comment. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `CommentObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-jsdpubl-42134f01709b" title="Jsd Public" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.jsdPublic`

            Jsd Public indicates whether the comment is visible to customers in Jira Service Desk. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports jsd public as true or false.
            * **Interpretation:** The provider supplies `jsdPublic` as a boolean per comment object record; false and missing are distinct when the field is optional. In Jira Cloud, jsd public is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-self-e64c2ae1c2be" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.self`

            Self records REST API URL for this comment. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-updatea-e1f9a0dd642c" title="Update Author" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.updateAuthor`

            Update Author records user who last updated the comment. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the comment object record to the provider-reported actor represented by update author.
            * **Interpretation:** The provider supplies `updateAuthor` as identity or attribution context on each comment object record. In Jira Cloud, update author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-updated-fe590724cc61" title="Updated" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.updated`

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

            * **Enables:** place issue records on a timeline by updated and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated` per comment object 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-jiracloud-issues-fields-comment-comments-visibil-908df366239f" title="Visibility" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.visibility`

            Visibility states visibility restriction for the comment. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported visibility attached to each comment object record.
            * **Interpretation:** The provider supplies `visibility` at comment object granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-visibil-27b3179001e2" title="Identifier" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.visibility.identifier`

            Identifier is the identifier of the group or role. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-visibil-73dd968f8e36" title="Type" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.visibility.type`

            Type states type of visibility restriction (group or role). It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported type attached to each visibility object record.
            * **Interpretation:** The provider supplies `type` at visibility object granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, type is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-comments-visibil-f34d33ea6112" title="Value" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.visibility.value`

            Value records name of the group or role. It preserves the recorded before, after, or contextual value needed to explain a change event.

            * **Enables:** compare the recorded value with the corresponding changed attribute when explaining an audit or changelog event.
            * **Interpretation:** The provider supplies `value` on each change record in the changed attribute's own type or display format; it is not normalized into a common unit.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-maxresults-068e75f21cfe" title="Max Results" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.maxResults`

            Max Results reports maximum number of comments returned. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported max results for each comment container record.
            * **Interpretation:** The provider supplies `maxResults` at comment container granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-startat-371a5e458e03" title="Start At" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.startAt`

            Start At identifies the pagination offset of the first comment returned in the embedded page. It locates that page within the issue's complete comment collection.

            * **Enables:** detect partial comment pages and continue interpretation with `maxResults` and `total`.
            * **Interpretation:** The provider supplies `startAt` as a zero-based pagination offset, not a comment count or business measure; zero denotes the first page.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-comment-total-5610bbdd7671" title="Total" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.total`

            Total reports the total number of comments on the issue. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total for each comment container record.
            * **Interpretation:** The provider supplies `total` at comment container granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-components-b8d307dbbd51" title="Components" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components`

            Components records components associated with this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested components object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `components` as a list on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-components-description-b35d8d9c2ec9" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-components-id-1ecd4a142f6c" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.id`

            ID is the unique identifier for the component. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `ComponentObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-components-name-ecfd8f62d566" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-components-self-635ee6b275d6" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.self`

            Self records REST API URL for this component. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-created-6011c6e315dc" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.created`

            Created records the timestamp when the issue was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per issue field 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-jiracloud-issues-fields-creator-19862cbf3824" title="Creator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.creator`

            Creator records user who created this issue. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the issue field record to the provider-reported actor represented by creator.
            * **Interpretation:** The provider supplies `creator` as identity or attribution context on each issue field record. In Jira Cloud, creator is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-description-6431f8f08123" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.description`

            Description records issue description in Atlassian Document Format (ADF). It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-duedate-b8cbe6ce618a" title="Duedate" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.duedate`

            Duedate records due date for the issue. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by duedate and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `duedate` per issue field record as a calendar date without a time of day; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-environment-8bf57a759339" title="Environment" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.environment`

            Environment states environment field in ADF format. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported environment value when describing their recorded state.
            * **Interpretation:** The provider supplies `environment` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, environment is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-6d47191b3132" title="Epic" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic`

            Epic records epic this issue belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested epic object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `epic` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-81fa1ae35d3e" title="Fields" icon="ranking-star" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields`

            Fields records summary fields of the referenced issue. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret fields according to the provider and Workspace configuration that produced each issue record.
            * **Interpretation:** Keys and value shapes within `fields` 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-jiracloud-issues-fields-epic-fields-issuetype-e0432b996ba5" title="Issuetype" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype`

            Issuetype states issue type of the referenced issue. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported issuetype value when describing their recorded state.
            * **Interpretation:** The provider supplies `issuetype` per issue reference summary field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, issuetype is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-de-4236a7555a0b" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-hi-670259729b1d" title="Hierarchy Level" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.hierarchyLevel`

            Hierarchy Level states hierarchy level of this issue type. It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud issue type hierarchy level exposed by the nested object.
            * **Interpretation:** The provider supplies `hierarchyLevel` per issue type object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, hierarchy level is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-ic-79d11728faea" title="Icon URL" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.iconUrl`

            Icon URL records URL of the issue type icon. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-id-541d02bfc025" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.id`

            ID is the unique identifier for the issue type. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `IssueTypeObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-na-b14bc2fc580e" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.name`

            Name states name of the issue type. It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud issue type name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per issue type object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-se-5cdadefe80e4" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.self`

            Self records REST API URL for this issue type. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-issuetype-su-afb04edb0b96" title="Subtask" icon="circle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.issuetype.subtask`

            Subtask indicates whether this issue type represents subtasks. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports subtask as true or false.
            * **Interpretation:** The provider supplies `subtask` as a boolean per issue type object record; false and missing are distinct when the field is optional. In Jira Cloud, subtask is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-priority-09ed8c0c9bbc" title="Priority" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.priority`

            Priority states priority of the referenced issue. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported priority value when describing their recorded state.
            * **Interpretation:** The provider supplies `priority` per issue reference summary field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, priority is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-priority-des-30109dceb6b9" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.priority.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-priority-ico-3da7b2752f92" title="Icon URL" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.priority.iconUrl`

            Icon URL records URL of the priority icon. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-priority-id-dedf75229374" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.priority.id`

            ID is the unique identifier for the priority. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `PriorityObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-priority-nam-70c83ba7e99a" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.priority.name`

            Name states name of the priority level. It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud priority name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per priority object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-priority-sel-cc204b2aa275" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.priority.self`

            Self records REST API URL for this priority. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-863661e1faad" title="Status" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status`

            Status states status of the referenced issue. It preserves the provider's current classification of this record.

            * **Enables:** filter issue records to a selected Jira status and group issue counts by that exact workflow classification.
            * **Interpretation:** The provider supplies `status` per issue reference summary field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, status is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-descr-23d23ff784cf" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.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 object record.
            * **Interpretation:** The provider supplies `description` at status object granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-iconu-1a67fe66971d" title="Icon URL" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.iconUrl`

            Icon URL records URL of the status icon. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-id-f8e56fc5f954" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.id`

            ID is the unique identifier for the status. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `StatusObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-name-99520b3fbec2" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.name`

            Name states display name of the status. It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud status name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per status object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-self-6dec5da3a918" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.self`

            Self records REST API URL for this status. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-statu-d3daf4a94ee0" title="Status Category" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.statusCategory`

            Status Category states category grouping for this status. It preserves the provider's current classification of this record.

            * **Enables:** filter issue records to a selected Jira status category and group issue counts by that exact workflow classification.
            * **Interpretation:** The provider supplies `statusCategory` per status object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, status category is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-statu-de536c585cb5" title="Color Name" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.statusCategory.colorName`

            Color Name records color associated with this category. It preserves the provider's visual treatment for the represented object.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-statu-baea736448a8" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.statusCategory.id`

            ID is the unique identifier for the status category. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `StatusCategoryObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-statu-5b4a91113b37" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.statusCategory.key`

            Key is the key of the status category. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `StatusCategoryObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-statu-793095f3f51d" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.statusCategory.name`

            Name states display name of the status category. It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud status category name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per status category object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-status-statu-eb69124cf777" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.status.statusCategory.self`

            Self records REST API URL for this status category. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-fields-summary-6783536037d4" title="Summary" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.fields.summary`

            Summary records summary of the referenced issue. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-id-90e75bbfe1d7" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.id`

            ID is the unique identifier of the referenced issue. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `IssueReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-key-ad88f398e0e7" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.key`

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

            * **Enables:** match issue 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 `IssueReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-epic-self-1b827ac8b626" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.self`

            Self records REST API URL for the referenced issue. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-c1208100d110" title="Fix Versions" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions`

            Fix Versions records fix versions associated with this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested fix versions object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `fixVersions` as a list on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-archived-c48712975fb6" title="Archived" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.archived`

            Archived indicates whether this version is archived. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports archived as true or false.
            * **Interpretation:** The provider supplies `archived` as a boolean per version object record; false and missing are distinct when the field is optional. In Jira Cloud, archived is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-description-7c12b0b6ede5" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-id-ffbf51fb9d9e" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.id`

            ID is the unique identifier for the version. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `VersionObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-name-e76c893e19fa" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-released-8491e9db23bd" title="Released" icon="terminal" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.released`

            Released indicates whether this version has been released. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports released as true or false.
            * **Interpretation:** The provider supplies `released` as a boolean per version object record; false and missing are distinct when the field is optional. In Jira Cloud, released is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-releasedate-ff6d11f2ad6e" title="Release Date" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.releaseDate`

            Release Date records release date of the version. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by release date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `releaseDate` per version object record as a calendar date without a time of day; missing values mean the event or boundary was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-fixversions-self-d3ea45dcf9df" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.self`

            Self records REST API URL for this version. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-cc8c9351ce86" title="Issuelinks" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks`

            Issuelinks records links to other issues. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested issuelinks object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `issuelinks` as a list on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-id-881e1abdc2b1" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.id`

            ID is the unique identifier for the issue link. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `IssueLinkObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-inwardissue-c7fcf431f779" title="Inward Issue" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue`

            Inward Issue captures the inward issue in the link relationship. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by inward issue on each issue link object record.
            * **Interpretation:** The provider returns `inwardIssue` as a nested object or reference on `IssueLinkObject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-outwardissue-de7e1e13c720" title="Outward Issue" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.outwardIssue`

            Outward Issue captures the outward issue in the link relationship. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by outward issue on each issue link object record.
            * **Interpretation:** The provider returns `outwardIssue` as a nested object or reference on `IssueLinkObject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-self-cbf512c1115a" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.self`

            Self records REST API URL for this link. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-type-a3e656baa854" title="Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type`

            Type states type of the link relationship. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported type value when describing their recorded state.
            * **Interpretation:** The provider supplies `type` per issue link object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-type-id-cd8648cd43b8" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type.id`

            ID is the unique identifier for the link type. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `IssueLinkTypeObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-type-inward-8c89a62ad1a2" title="Inward" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type.inward`

            Inward records inward description (e.g., 'is blocked by'). It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-type-name-4493e392ea5e" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-type-outward-e02afaf53b60" title="Outward" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type.outward`

            Outward records outward description (e.g., 'blocks'). It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuelinks-type-self-74f70c6da053" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type.self`

            Self records REST API URL for this link type. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-issuetype-12ac179ccbe0" title="Issuetype" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuetype`

            Issuetype states type of issue (Bug, Story, Task, etc.). It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported issuetype value when describing their recorded state.
            * **Interpretation:** The provider supplies `issuetype` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, issuetype is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-labels-427096654cce" title="Labels" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.labels`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-lastviewed-a912f14bda38" title="Last Viewed" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.lastViewed`

            Last Viewed records the timestamp when the current user last viewed this issue. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by last viewed and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastViewed` per issue field 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-jiracloud-issues-fields-parent-f2a3b7c91c4b" title="Parent" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.parent`

            Parent records parent issue reference (for subtasks or child issues in next-gen projects). It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by parent on each issue field record.
            * **Interpretation:** The provider returns `parent` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-priority-846541da22c4" title="Priority" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.priority`

            Priority states priority level of the issue. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported priority value when describing their recorded state.
            * **Interpretation:** The provider supplies `priority` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, priority is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-progress-edfc6c1e40f5" title="Progress" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.progress`

            Progress groups time spent, total estimated time, and completion percentage for the issue itself. It preserves the time-tracking state without including subtask rollups.

            * **Enables:** compare spent time with the issue estimate and identify incomplete or overrunning work.
            * **Interpretation:** The provider supplies `progress` as a nested progress object whose time fields are seconds and whose percent field uses a 0–100 scale; absence means no issue progress was reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-cee433f29b0e" title="Project" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project`

            Project records project this issue belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each issue field record with the specific provider container named by project.
            * **Interpretation:** The provider returns `project` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-avatarurls-57069147c099" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.avatarUrls`

            Avatar URLs records project avatar URLs. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-id-de6851110339" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.id`

            ID is the unique identifier for the project. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `ProjectObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-key-910d261b67f7" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.key`

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

            * **Enables:** match issue 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 `ProjectObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-name-ec7a53ecb001" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.name`

            Name records display 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 object record.
            * **Interpretation:** The provider supplies `name` at project object granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-projectcategory-3f085a6df87a" title="Project Category" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory`

            Project Category states category of the project. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported project category value when describing their recorded state.
            * **Interpretation:** The provider supplies `projectCategory` per project object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, project category is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-projectcategory--fe3c7e791233" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-projectcategory--3f35aaa17251" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.id`

            ID is the unique identifier for the project category. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `ProjectCategoryObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-projectcategory--5dccca0f8de2" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.name`

            Name states name of the project category. It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud project category name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per project category object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-projectcategory--86c6a13fe5c5" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.self`

            Self records REST API URL for this category. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-projecttypekey-51d6a3a71d24" title="Project Type Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectTypeKey`

            Project Type Key identifies type of project (software, business, `service_desk`). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-self-d8871589ec65" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.self`

            Self records REST API URL for this project. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-project-simplified-622c7f54ab03" title="Simplified" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.simplified`

            Simplified indicates whether this is a next-gen (simplified) project. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports simplified as true or false.
            * **Interpretation:** The provider supplies `simplified` as a boolean per project object record; false and missing are distinct when the field is optional. In Jira Cloud, simplified is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-reporter-4aa62798c136" title="Reporter" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.reporter`

            Reporter records user who reported this issue. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the issue field record to the provider-reported person or account represented by reporter.
            * **Interpretation:** The provider supplies `reporter` as identity or attribution context on each issue field record. In Jira Cloud, reporter is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-resolution-75bc4bdfe489" title="Resolution" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolution`

            Resolution states resolution of the issue if resolved. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported resolution value when describing their recorded state.
            * **Interpretation:** The provider supplies `resolution` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, resolution is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-resolution-description-0b729346db94" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolution.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-resolution-id-3a2aaa02cc6b" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolution.id`

            ID is the unique identifier for the resolution. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `ResolutionObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-resolution-name-148119626257" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolution.name`

            Name states name of the resolution (e.g., Done, Won't Do). It preserves the provider's current classification of this record.

            * **Enables:** filter and group issue records by the Jira Cloud resolution name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per resolution object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-resolution-self-72b874d9093b" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolution.self`

            Self records REST API URL for this resolution. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-resolutiondate-59ebc99e89ec" title="Resolutiondate" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolutiondate`

            Resolutiondate records the timestamp when the issue was resolved. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by resolutiondate and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `resolutiondate` per issue field 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-jiracloud-issues-fields-security-034e589f577e" title="Security" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security`

            Security states security level of this issue. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported security value when describing their recorded state.
            * **Interpretation:** The provider supplies `security` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, security is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-security-description-42856daa556b" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-security-id-3b3c98490fd5" title="ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security.id`

            ID is the unique identifier for the security level. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `SecurityLevelObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-security-name-a56ec42c79f9" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-security-self-323a9e54c10f" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security.self`

            Self records REST API URL for this security level. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-sprint-b440985c4434" title="Sprint" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.sprint`

            Sprint states active sprint this issue is in (from Jira Software). It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported sprint value when describing their recorded state.
            * **Interpretation:** The provider supplies `sprint` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, sprint is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-status-38eda6338a55" title="Status" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.status`

            Status states current workflow status of the issue. It preserves the provider's current classification of this record.

            * **Enables:** filter issue records to a selected Jira status and group issue counts by that exact workflow classification.
            * **Interpretation:** The provider supplies `status` per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, status is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-statuscategorychangedate-a78fd37357e1" title="Statuscategorychangedate" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.statuscategorychangedate`

            Statuscategorychangedate records the timestamp when the status category last changed. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by statuscategorychangedate and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `statuscategorychangedate` per issue field 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-jiracloud-issues-fields-storypoints-69e79f714c14" title="Story Points" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.storyPoints`

            Story Points records story points estimate (custom field, commonly mapped). It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret story points according to the provider and Workspace configuration that produced each issue record.
            * **Interpretation:** Keys and value shapes within `storyPoints` 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-jiracloud-issues-fields-subtasks-bd7446b5be30" title="Subtasks" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.subtasks`

            Subtasks records subtasks of this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** reconstruct the parent-child structure expressed by subtasks on each issue field record.
            * **Interpretation:** The provider returns `subtasks` as a list on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-summary-06e9270d5ba5" title="Summary" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.summary`

            Summary records short title describing the issue. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timeestimate-44a0269af7b4" title="Timeestimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timeestimate`

            Timeestimate reports remaining time estimate in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by timeestimate across issue records.
            * **Interpretation:** The provider supplies `timeestimate` per issue field record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timeoriginalestimate-e13bd5583101" title="Timeoriginalestimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timeoriginalestimate`

            Timeoriginalestimate reports original time estimate in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by timeoriginalestimate across issue records.
            * **Interpretation:** The provider supplies `timeoriginalestimate` per issue field record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timespent-e50b73004ac3" title="Timespent" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timespent`

            Timespent reports the total time spent in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by timespent across issue records.
            * **Interpretation:** The provider supplies `timespent` per issue field record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-6521af07acf7" title="Timetracking" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking`

            Timetracking records time tracking information. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested timetracking object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `timetracking` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-originalest-cd56debd6812" title="Original Estimate" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.originalEstimate`

            Original Estimate records the issue's original planned duration in Jira's human-readable format. It preserves the planning interval alongside its seconds representation.

            * **Enables:** compare planned effort across issues and display the estimate in the provider's own duration syntax.
            * **Interpretation:** The provider supplies `originalEstimate` as duration text such as `5d 2h`; consumers must use Jira's unit conventions rather than treat the string as an ordinal.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-originalest-761a1bb22690" title="Original Estimate Seconds" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.originalEstimateSeconds`

            Original Estimate Seconds reports original estimate in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by original estimate seconds across issue records.
            * **Interpretation:** The provider supplies `originalEstimateSeconds` per time tracking object record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-remaininges-e986bfe92099" title="Remaining Estimate" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.remainingEstimate`

            Remaining Estimate records the issue's remaining planned duration in Jira's human-readable format. It preserves the current forecast alongside its seconds representation.

            * **Enables:** compare outstanding effort across issues and display the estimate in the provider's own duration syntax.
            * **Interpretation:** The provider supplies `remainingEstimate` as provider-formatted duration text; consumers must use Jira's unit conventions rather than treat the string as an ordinal.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-remaininges-02fb8de550a9" title="Remaining Estimate Seconds" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.remainingEstimateSeconds`

            Remaining Estimate Seconds reports remaining estimate in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by remaining estimate seconds across issue records.
            * **Interpretation:** The provider supplies `remainingEstimateSeconds` per time tracking object record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-timespent-e83bb8971121" title="Time Spent" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.timeSpent`

            Time Spent reports human-readable total time spent. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by time spent across issue records.
            * **Interpretation:** The provider supplies `timeSpent` per time tracking object record in the unit stated by the provider description; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-timetracking-timespentse-a840663a9b67" title="Time Spent Seconds" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.timeSpentSeconds`

            Time Spent Seconds reports the total time spent in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by time spent seconds across issue records.
            * **Interpretation:** The provider supplies `timeSpentSeconds` per time tracking object record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-updated-efed0f091c48" title="Updated" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.updated`

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

            * **Enables:** place issue records on a timeline by updated and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated` per issue field 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-jiracloud-issues-fields-versions-9e0cf187f912" title="Versions" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.versions`

            Versions records affects versions associated with this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested versions object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `versions` as a list on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-votes-242d67ed7d31" title="Votes" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.votes`

            Votes records vote information for this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested votes object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `votes` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-votes-hasvoted-2508e89167da" title="Has Voted" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.votes.hasVoted`

            Has Voted indicates whether the current user has voted. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports has voted as true or false.
            * **Interpretation:** The provider supplies `hasVoted` as a boolean per votes object record; false and missing are distinct when the field is optional. In Jira Cloud, has voted is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-votes-self-c7b0745a36a8" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.votes.self`

            Self records REST API URL for votes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-votes-votes-4936e934fb72" title="Votes" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.votes.votes`

            Votes reports the number of votes. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported votes for each votes object record.
            * **Interpretation:** The provider supplies `votes` at votes object granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-watches-eab59a6fbfcc" title="Watches" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.watches`

            Watches records watch information for this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested watches object into its declared child fields for each issue field record.
            * **Interpretation:** The provider returns `watches` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-watches-iswatching-106abb18e65a" title="Is Watching" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.watches.isWatching`

            Is Watching indicates whether the current user is watching. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports is watching as true or false.
            * **Interpretation:** The provider supplies `isWatching` as a boolean per watches object record; false and missing are distinct when the field is optional. In Jira Cloud, is watching is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-watches-self-e95c833aa17d" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.watches.self`

            Self records REST API URL for watches. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-watches-watchcount-90f8c00bc704" title="Watch Count" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.watches.watchCount`

            Watch Count reports the number of watchers. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported watch count for each watches object record.
            * **Interpretation:** The provider supplies `watchCount` at watches object granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-45af99ba68d2" title="Worklog" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog`

            Worklog records worklogs on this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested worklog records contained by each issue field record.
            * **Interpretation:** The provider returns `worklog` as a nested object or reference on `IssueFields`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-maxresults-59b2dcd5f774" title="Max Results" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.maxResults`

            Max Results reports maximum number of worklogs returned. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported max results for each worklog container record.
            * **Interpretation:** The provider supplies `maxResults` at worklog container granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-startat-6218a85ad258" title="Start At" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.startAt`

            Start At identifies the pagination offset of the first worklog returned in the embedded page. It locates that page within the issue's complete worklog collection.

            * **Enables:** detect partial worklog pages and continue interpretation with `maxResults` and `total`.
            * **Interpretation:** The provider supplies `startAt` as a zero-based pagination offset, not a worklog count or business measure; zero denotes the first page.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-total-c72460add6e4" title="Total" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.total`

            Total reports the total number of worklogs on the issue. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total for each worklog container record.
            * **Interpretation:** The provider supplies `total` at worklog container granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-2841fed7224e" title="Worklogs" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs`

            Worklogs records list of worklogs on the issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested worklogs records contained by each worklog container record.
            * **Interpretation:** The provider returns `worklogs` as a list on `WorklogContainer`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-author-1b4f762c58a8" title="Author" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.author`

            Author records user who created the worklog. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the worklog object record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each worklog object record. In Jira Cloud, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-comment-e02de07e8499" title="Comment" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.comment`

            Comment records worklog comment in ADF format. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-created-1d65cd5da3a9" title="Created" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.created`

            Created records the timestamp when the worklog was created. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by created and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `created` per worklog object 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-jiracloud-issues-fields-worklog-worklogs-id-18629cb44a0f" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.id`

            ID is the unique identifier for the worklog. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `WorklogObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-issueid-8f296c363b94" title="Issue ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.issueId`

            Issue ID is the ID of the issue this worklog belongs to. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match issue 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 `WorklogObject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-self-40771fe96d5f" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.self`

            Self records REST API URL for this worklog. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-started-949c21521e11" title="Started" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.started`

            Started records the timestamp when the work was started. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place issue records on a timeline by started and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `started` per worklog object 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-jiracloud-issues-fields-worklog-worklogs-timespe-408cbe7b41d2" title="Time Spent" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.timeSpent`

            Time Spent reports human-readable time spent (e.g., '3h 20m'). It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by time spent across issue records.
            * **Interpretation:** The provider supplies `timeSpent` per worklog object record in the unit stated by the provider description; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-timespe-d4f34668c059" title="Time Spent Seconds" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.timeSpentSeconds`

            Time Spent Seconds reports time spent in seconds. It preserves the elapsed interval reported for this record.

            * **Enables:** compare the provider-recorded interval represented by time spent seconds across issue records.
            * **Interpretation:** The provider supplies `timeSpentSeconds` per worklog object record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-updatea-6525eb0691c0" title="Update Author" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.updateAuthor`

            Update Author records user who last updated the worklog. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the worklog object record to the provider-reported actor represented by update author.
            * **Interpretation:** The provider supplies `updateAuthor` as identity or attribution context on each worklog object record. In Jira Cloud, update author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-worklog-worklogs-updated-c2f87658b2b7" title="Updated" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.updated`

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

            * **Enables:** place issue records on a timeline by updated and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `updated` per worklog object 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-jiracloud-issues-fields-worklog-worklogs-visibil-4ef97258a76e" title="Visibility" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.visibility`

            Visibility states visibility restriction for the worklog. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported visibility attached to each worklog object record.
            * **Interpretation:** The provider supplies `visibility` at worklog object granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-fields-workratio-e79ec70639c9" title="Workratio" icon="ranking-star" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.workratio`

            Workratio reports the issue's work ratio as a percentage. It relates recorded work to the available estimate.

            * **Enables:** identify issues consuming more or less effort than planned and separate issues that lack an estimate.
            * **Interpretation:** The provider supplies `workratio` as an integer percentage and uses `-1` when no estimate applies; `-1`, zero, and missing have different meanings.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-id-a5ed9f6f40b6" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.id`

            ID is the unique numeric identifier for the issue. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-issues-key-36849f76ca2d" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.key`

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

            * **Enables:** match issue 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 `JiraCloudIssue`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-names-e3af7f6a14cb" title="Names" icon="arrow-trend-up" iconType="sharp-duotone-solid">
            Developer identifier: `issues.names`

            Names records map of field IDs to human-readable field names, present when `expand=names` is requested. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact names when validating the configuration or technical definition of a jira cloud issue record.
            * **Interpretation:** The provider supplies `names` as configuration or technical metadata on `JiraCloudIssue`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-operations-200b1f03cc16" title="Operations" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `issues.operations`

            Operations records available operations on this issue. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact operations when validating the configuration or technical definition of a jira cloud issue record.
            * **Interpretation:** The provider supplies `operations` as configuration or technical metadata on `JiraCloudIssue`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-project-key-c48e146866a3" title="Project Key" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `issues.project_key`

            Project Key identifies parent key injected by the ingestor from the projects to issues 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 issue records to provider records that carry the same project key, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `project_key` as a record-level identifier on `JiraCloudIssue`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-renderedfields-7cdf601c0be2" title="Rendered Fields" icon="chart-pie" iconType="sharp-duotone-solid">
            Developer identifier: `issues.renderedFields`

            Rendered Fields records HTML-rendered versions of fields, present when expand=`renderedFields` is requested. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact rendered fields when validating the configuration or technical definition of a jira cloud issue record.
            * **Interpretation:** The provider supplies `renderedFields` as configuration or technical metadata on `JiraCloudIssue`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-self-f21cc5a61cce" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.self`

            Self records REST API URL for this issue. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-e1b4789f18df" title="Transitions" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions`

            Transitions records available workflow transitions for this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** expand the nested transitions object into its declared child fields for each jira cloud issue record.
            * **Interpretation:** The provider returns `transitions` as a list on `JiraCloudIssue`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-hasscreen-7104f87df912" title="Has Screen" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.hasScreen`

            Has Screen indicates whether the transition has an associated screen. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports has screen as true or false.
            * **Interpretation:** The provider supplies `hasScreen` as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, has screen is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-id-61d9ef8ac552" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.id`

            ID is the unique identifier for the transition. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-isconditional-1057b32e6f39" title="Is Conditional" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.isConditional`

            Is Conditional indicates whether this transition has conditions. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports is conditional as true or false.
            * **Interpretation:** The provider supplies `isConditional` as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, is conditional is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-isglobal-c53d86284166" title="Is Global" icon="brackets-curly" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.isGlobal`

            Is Global indicates whether this is a global transition. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports is global as true or false.
            * **Interpretation:** The provider supplies `isGlobal` as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, is global is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-isinitial-94397bc39709" title="Is Initial" icon="code-merge" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.isInitial`

            Is Initial indicates whether this is the initial transition. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select issue records for which the provider reports is initial as true or false.
            * **Interpretation:** The provider supplies `isInitial` as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, is initial is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-name-d38d2ec7ba91" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-issues-transitions-to-dc1e885f85c3" title="To" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.transitions.to`

            To states target status of the transition. It preserves the provider's current classification of this record.

            * **Enables:** separate issue records by the exact provider-reported to value when describing their recorded state.
            * **Interpretation:** The provider supplies `to` per issue transition record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, to is the work record's classification, not an individual-performance measure.
          </Accordion>
        </AccordionGroup>
      </Accordion>

      <Accordion id="provider-permission-tap-jiracloud-projects-2d27ecc77aba" title="Projects" icon="route" iconType="sharp-duotone-solid">
        Developer identifier: `projects`

        Projects contain Jira Cloud projects.

        * **Enables:** map Jira Cloud issues to their project containers and project metadata.
        * **Scope:** Reads the declared collection through `GET /rest/api/3/project/search` as a full snapshot. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-jiracloud-projects-archived-53b48e09a475" title="Archived" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archived`

            Archived indicates whether the project is archived. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports archived as true or false.
            * **Interpretation:** The provider supplies `archived` as a boolean per jira cloud project record; false and missing are distinct when the field is optional. In Jira Cloud, archived is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-bf30f2d6cd13" title="Archived By" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy`

            Archived By captures the user who archived the project. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported archived by value when describing their recorded state.
            * **Interpretation:** The provider supplies `archivedBy` per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, archived by is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-accountid-0beacc15c1eb" title="Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.accountId`

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

            * **Enables:** match project 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 `UserSummary`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-accounttype-00b9fc441fb0" title="Account Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.accountType`

            Account Type states type of the user account. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported account type value when describing their recorded state.
            * **Interpretation:** The provider supplies `accountType` per user summary record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, account type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-active-354f9c84bc0f" title="Active" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.active`

            Active indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per user summary record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-avatarurls-070d7fb0cc75" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.avatarUrls`

            Avatar URLs records avatar URLs for the user in various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-avatarurls-16x16-0f9176953dc4" title="16x16" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.avatarUrls.16x16`

            16x16 records URL for the 16x16 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-avatarurls-24x24-24cdda7b078d" title="24x24" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.avatarUrls.24x24`

            24x24 records URL for the 24x24 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-avatarurls-32x32-492d96e7a73e" title="32x32" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.avatarUrls.32x32`

            32x32 records URL for the 32x32 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-avatarurls-48x48-e2ac77f48124" title="48x48" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.avatarUrls.48x48`

            48x48 records URL for the 48x48 pixel avatar. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-displayname-c1558235b778" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.displayName`

            Display Name records display name of the user. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user summary record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each user summary record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-emailaddress-85c0bfc8ef16" title="Email Address" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.emailAddress`

            Email Address records email address of the user (if visible). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the user summary record to the provider-reported person or account represented by email address.
            * **Interpretation:** The provider supplies `emailAddress` as identity or attribution context on each user summary record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-self-0a9be5f5eb46" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.self`

            Self records REST API URL for this 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 user summary record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each user summary record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archivedby-timezone-5a9b8c8fa99e" title="Time Zone" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedBy.timeZone`

            Time Zone records time zone of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for projects using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per user summary record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-archiveddate-91a0bf6a0955" title="Archived Date" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.archivedDate`

            Archived Date records the date when the project was archived. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported archived date value when describing their recorded state.
            * **Interpretation:** The provider supplies `archivedDate` per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, archived date is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-avatarurls-18f7af5e15e4" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.avatarUrls`

            Avatar URLs records URLs for the project avatar in various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-deleted-d0e7baccb754" title="Deleted" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `projects.deleted`

            Deleted indicates whether the project has been moved to the trash and is pending deletion. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports deleted as true or false.
            * **Interpretation:** The provider supplies `deleted` as a boolean per jira cloud project record; false and missing are distinct when the field is optional. In Jira Cloud, deleted is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-deletedby-3fe8f2234866" title="Deleted By" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `projects.deletedBy`

            Deleted By captures the user who deleted the project. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported deleted by value when describing their recorded state.
            * **Interpretation:** The provider supplies `deletedBy` per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, deleted by is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-deleteddate-189e683a8b8e" title="Deleted Date" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.deletedDate`

            Deleted Date records the date when the project was moved to the trash. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported deleted date value when describing their recorded state.
            * **Interpretation:** The provider supplies `deletedDate` per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, deleted date is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-description-0249e8f5f961" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.description`

            Description records project description text, may contain Atlassian Document Format or plain text. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiracloud-projects-entityid-b6ce6e87ca99" title="Entity ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.entityId`

            Entity ID identifies entity ID used for cross-product identification. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-projects-expand-11731f7cd173" title="Expand" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `projects.expand`

            Expand records comma-separated list of expanded fields included in this response. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact expand when validating the configuration or technical definition of a jira cloud project record.
            * **Interpretation:** The provider supplies `expand` as configuration or technical metadata on `JiraCloudProject`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-id-a3efef8b13ce" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.id`

            ID is the unique numeric identifier for the project (returned as string). It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match project 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 `JiraCloudProject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-insight-cff5ba87dae5" title="Provider Attribute" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.insight`

            Provider Attribute records insight information about the project's recent activity. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira cloud project record with the specific provider container named by provider attribute.
            * **Interpretation:** The provider returns `insight` as a nested object or reference on `JiraCloudProject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-insight-lastissueupdatetime-1150859f76af" title="Last Issue Update Time" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.insight.lastIssueUpdateTime`

            Last Issue Update Time records the timestamp of the most recent issue update in the project. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place project records on a timeline by last issue update time and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `lastIssueUpdateTime` per project insight 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-jiracloud-projects-insight-totalissuecount-82af5898be0d" title="Total Issue Count" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `projects.insight.totalIssueCount`

            Total Issue Count reports the total number of issues in the project. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported total issue count for each project insight record.
            * **Interpretation:** The provider supplies `totalIssueCount` at project insight granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-isprivate-d183a5f80811" title="Is Private" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.isPrivate`

            Is Private indicates whether the project is private and only visible to its members. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported is private attached to each jira cloud project record.
            * **Interpretation:** The provider supplies `isPrivate` at jira cloud project granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-10e8ce89bdd8" title="Issue Types" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes`

            Issue Types records issue types available in this project (present when expand includes `issueTypes`). It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira cloud project record with the specific provider container named by issue types.
            * **Interpretation:** The provider returns `issueTypes` as a list on `JiraCloudProject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-description-ee639f07647b" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-hierarchylevel-c55346d8278c" title="Hierarchy Level" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.hierarchyLevel`

            Hierarchy Level states hierarchy level of this issue type. It preserves the provider's current classification of this record.

            * **Enables:** filter and group project records by the Jira Cloud project issue type hierarchy level exposed by the nested object.
            * **Interpretation:** The provider supplies `hierarchyLevel` per project issue type record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, hierarchy level is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-iconurl-c2ca30af5b8f" title="Icon URL" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.iconUrl`

            Icon URL records URL of the issue type icon. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-id-96f5613b0c27" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.id`

            ID is the unique identifier for the issue type. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-name-38d99bde87a6" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.name`

            Name states name of the issue type. It preserves the provider's current classification of this record.

            * **Enables:** filter and group project records by the Jira Cloud project issue type name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per project issue type record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-self-fff92ee30637" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.self`

            Self records REST API URL for this issue type. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-issuetypes-subtask-66dd79f246b5" title="Subtask" icon="circle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.subtask`

            Subtask indicates whether this issue type represents subtasks. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports subtask as true or false.
            * **Interpretation:** The provider supplies `subtask` as a boolean per project issue type record; false and missing are distinct when the field is optional. In Jira Cloud, subtask is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-key-c39fa22fed8d" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.key`

            Key identifies short alphanumeric project key (e.g., PROJ) used in issue keys. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-9d6d9a632124" title="Landing Page Info" icon="arrow-trend-up" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo`

            Landing Page Info records information about the project landing page configuration. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact landing page info when validating the configuration or technical definition of a jira cloud project record.
            * **Interpretation:** The provider supplies `landingPageInfo` as configuration or technical metadata on `JiraCloudProject`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-boardid-aaeea6f46de9" title="Board ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo.boardId`

            Board ID identifies board ID if the landing page is a board. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-projectkey-fa82bb504b23" title="Project Key" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo.projectKey`

            Project Key identifies project key associated with the landing page. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-projecttype-79458e6504a5" title="Project Type" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo.projectType`

            Project Type states project type for the landing page. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported project type value when describing their recorded state.
            * **Interpretation:** The provider supplies `projectType` per project landing page info record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, project type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-queueid-daf37c74f1b0" title="Queue ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo.queueId`

            Queue ID identifies queue ID if the landing page is a service desk queue. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-simplified-b4c00407a3c2" title="Simplified" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo.simplified`

            Simplified indicates whether the landing page uses simplified view. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports simplified as true or false.
            * **Interpretation:** The provider supplies `simplified` as a boolean per project landing page info record; false and missing are distinct when the field is optional. In Jira Cloud, simplified is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-landingpageinfo-url-934092a77b97" title="URL" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.landingPageInfo.url`

            URL records URL of the project landing page. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-lead-1955d948e93a" title="Lead" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead`

            Lead captures the user designated as the project lead. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira cloud project record to the provider-reported person or account represented by lead.
            * **Interpretation:** The provider supplies `lead` as identity or attribution context on each jira cloud project record. In Jira Cloud, lead is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-accountid-40cbdcf9a110" title="Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.accountId`

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

            * **Enables:** match project 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 `ProjectLead`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-accounttype-76badc472fb9" title="Account Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.accountType`

            Account Type states type of the user account. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported account type value when describing their recorded state.
            * **Interpretation:** The provider supplies `accountType` per project lead record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, account type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-active-08553c9eac4b" title="Active" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.active`

            Active indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per project lead record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-avatarurls-b1ddca6295c1" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.avatarUrls`

            Avatar URLs records avatar URLs for the project lead in various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-lead-displayname-e76bee13c0c4" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.displayName`

            Display Name records display name of the project lead. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the project lead record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each project lead record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-emailaddress-3d24f68076d8" title="Email Address" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.emailAddress`

            Email Address records email address of the project lead (if visible). It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the project lead record to the provider-reported person or account represented by email address.
            * **Interpretation:** The provider supplies `emailAddress` as identity or attribution context on each project lead record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-self-91d6c4f8205c" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.self`

            Self records REST API URL for this 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 project lead record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each project lead record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-lead-timezone-2e9abe35cbac" title="Time Zone" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead.timeZone`

            Time Zone records time zone of the project lead. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for projects using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per project lead record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-name-2cc456a56629" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.name`

            Name records display 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 jira cloud project record.
            * **Interpretation:** The provider supplies `name` at jira cloud project granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-permissions-8b249c3ea02b" title="Permissions" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions`

            Permissions states permissions the current user has on this project. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported permissions attached to each jira cloud project record.
            * **Interpretation:** The provider supplies `permissions` at jira cloud project granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-permissions-canedit-7b7fa53d5194" title="Can Edit" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.permissions.canEdit`

            Can Edit indicates whether the user can edit the project configuration. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports can edit as true or false.
            * **Interpretation:** The provider supplies `canEdit` as a boolean per project permission record; false and missing are distinct when the field is optional. In Jira Cloud, can edit is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-projectcategory-ce97a51491c3" title="Project Category" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory`

            Project Category captures the category assigned to this project. It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported project category value when describing their recorded state.
            * **Interpretation:** The provider supplies `projectCategory` per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, project category is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-projectcategory-description-8c0f6f2504db" title="Description" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory.description`

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

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

          <Accordion id="provider-permission-field-jiracloud-projects-projectcategory-id-d8cc11ebfcb4" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory.id`

            ID is the unique identifier for the project category. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match project 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 `ProjectCategory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-projectcategory-name-fd80d1ced84a" title="Name" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory.name`

            Name states name of the project category. It preserves the provider's current classification of this record.

            * **Enables:** filter and group project records by the Jira Cloud project category name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per project category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-projectcategory-self-1460fd455f83" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory.self`

            Self records REST API URL for this project category resource. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-projectkeys-110976d812ee" title="Project Keys" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectKeys`

            Project Keys records alternate project keys for this project (present when expand includes `projectKeys`). It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira cloud project record with the specific provider container named by project keys.
            * **Interpretation:** The provider returns `projectKeys` as a list on `JiraCloudProject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-projecttypekey-56372367822b" title="Project Type Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectTypeKey`

            Project Type Key identifies type of project (software, `service_desk`, business). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-projects-properties-2681221b9e4c" title="Properties" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.properties`

            Properties records arbitrary project properties as key-value metadata. It retains configured attributes whose keys or shape are not fixed by this base schema.

            * **Enables:** interpret properties according to the provider and Workspace configuration that produced each project record.
            * **Interpretation:** Keys and value shapes within `properties` 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-jiracloud-projects-retentiontilldate-df8f15ee1683" title="Retention Till Date" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.retentionTillDate`

            Retention Till Date records the date until which a deleted project will be retained before permanent deletion. It anchors the named event or boundary on the record's timeline.

            * **Enables:** place project records on a timeline by retention till date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `retentionTillDate` per jira cloud project 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-jiracloud-projects-self-8e8c6e70a674" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.self`

            Self records REST API URL for this 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 jira cloud project record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira cloud project record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-simplified-9c9b52bba737" title="Simplified" icon="code-commit" iconType="sharp-duotone-solid">
            Developer identifier: `projects.simplified`

            Simplified indicates whether the project is a simplified (next-gen/team-managed) project. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select project records for which the provider reports simplified as true or false.
            * **Interpretation:** The provider supplies `simplified` as a boolean per jira cloud project record; false and missing are distinct when the field is optional. In Jira Cloud, simplified is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-style-abeffa07b53b" title="Style" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.style`

            Style states project style indicating management methodology (classic or next-gen). It preserves the provider's current classification of this record.

            * **Enables:** separate project records by the exact provider-reported style value when describing their recorded state.
            * **Interpretation:** The provider supplies `style` per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, style is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-projects-url-1294ac910cd6" title="URL" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.url`

            URL records URL to the project in the Jira web interface. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-projects-uuid-1a532495799f" title="UUID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.uuid`

            UUID is the unique UUID for the project. It is needed to resolve references that repeat the same provider identifier.

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

      <Accordion id="provider-permission-tap-jiracloud-users-f4ffeee7f159" title="Users" icon="people-group" iconType="sharp-duotone-solid">
        Developer identifier: `users`

        Users contain Jira Cloud users.

        * **Enables:** resolve Jira Cloud account identities referenced by issues, comments, and changes.
        * **Scope:** Reads the declared collection through `GET /rest/api/3/users/search` as a full snapshot. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

        <AccordionGroup>
          <Accordion id="provider-permission-field-jiracloud-users-accountid-9cc309a10311" title="Account ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.accountId`

            Account ID is the unique Atlassian account identifier for the user. Primary key for cross-system identity resolution across Atlassian products. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiracloud-users-accounttype-a4f08f63a824" title="Account Type" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.accountType`

            Account Type states type of account: atlassian (normal user), app (service/bot account), or customer (Jira Service Management customer). It preserves the provider's current classification of this record.

            * **Enables:** separate user records by the exact provider-reported account type value when describing their recorded state.
            * **Interpretation:** The provider supplies `accountType` per jira cloud user record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, account type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-active-00c4951a241c" title="Active" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `users.active`

            Active indicates whether the user account is currently active. False indicates a deactivated account. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports active as true or false.
            * **Interpretation:** The provider supplies `active` as a boolean per jira cloud user record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-30a43237d16f" title="Application Roles" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles`

            Application Roles states application roles assigned to the user. Only present when expanded. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported application roles attached to each jira cloud user record.
            * **Interpretation:** The provider supplies `applicationRoles` at jira cloud user granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, application roles is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-callback-55391ec1c5b7" title="Callback" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.callback`

            Callback records callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact callback when validating the configuration or technical definition of a paginated application role list record.
            * **Interpretation:** The provider supplies `callback` as configuration or technical metadata on `PaginatedApplicationRoleList`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-d564e44ef0e5" title="Items" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items`

            Items captures the list of application role items. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported items attached to each paginated application role list record.
            * **Interpretation:** The provider supplies `items` at paginated application role list granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, items is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-defaultgr-0850723afab0" title="Default Groups" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.defaultGroups`

            Default Groups states default groups for this application role. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported default groups attached to each application role item record.
            * **Interpretation:** The provider supplies `defaultGroups` at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, default groups is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-defined-13b413ebcda5" title="Defined" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.defined`

            Defined indicates whether this role is defined. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports defined as true or false.
            * **Interpretation:** The provider supplies `defined` as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, defined is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-groups-bf5a35a572a5" title="Groups" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.groups`

            Groups states groups associated with this application role. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported groups attached to each application role item record.
            * **Interpretation:** The provider supplies `groups` at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, groups is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-hasunlimi-75124b3d1154" title="Has Unlimited Seats" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.hasUnlimitedSeats`

            Has Unlimited Seats indicates whether this role has unlimited seats. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports has unlimited seats as true or false.
            * **Interpretation:** The provider supplies `hasUnlimitedSeats` as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, has unlimited seats is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-key-ee596d4efec5" title="Key" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.key`

            Key captures the key of the application role. It is needed to resolve references that repeat the same provider identifier.

            * **Enables:** match user 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 `ApplicationRoleItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-name-e4d416445b31" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.name`

            Name captures the display name of the application role. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported name attached to each application role item record.
            * **Interpretation:** The provider supplies `name` at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, name is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-numberofs-1b66b909bbc6" title="Number Of Seats" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.numberOfSeats`

            Number Of Seats reports the number of seats for this application role. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported number of seats attached to each application role item record.
            * **Interpretation:** The provider supplies `numberOfSeats` at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, number of seats is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-platform-6068f6024f2e" title="Platform" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.platform`

            Platform indicates whether this is a platform role. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports platform as true or false.
            * **Interpretation:** The provider supplies `platform` as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, platform is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-remaining-0d270bda33e6" title="Remaining Seats" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.remainingSeats`

            Remaining Seats reports the number of remaining seats for this application role. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported remaining seats attached to each application role item record.
            * **Interpretation:** The provider supplies `remainingSeats` at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, remaining seats is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-selectedb-c1a85ccadf59" title="Selected By Default" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.selectedByDefault`

            Selected By Default indicates whether this role is selected by default. It preserves the provider-reported yes-or-no condition for this record.

            * **Enables:** select user records for which the provider reports selected by default as true or false.
            * **Interpretation:** The provider supplies `selectedByDefault` as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, selected by default is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-usercount-4b8d9416d6de" title="User Count" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.userCount`

            User Count reports the number of users with this application role. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported user count attached to each application role item record.
            * **Interpretation:** The provider supplies `userCount` at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, user count is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-items-usercount-e6749f9f9626" title="User Count Description" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.userCountDescription`

            User Count Description reports human-readable description of the user count. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported user count description for each application role item record.
            * **Interpretation:** The provider supplies `userCountDescription` at application role item granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-max-results-956658a3d891" title="Max Results" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.max-results`

            Max Results reports maximum number of results per page. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported max results for each paginated application role list record.
            * **Interpretation:** The provider supplies `max-results` at paginated application role list granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-pagingcallback-4a6d7d7d9127" title="Paging Callback" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.pagingCallback`

            Paging Callback records paging callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact paging callback when validating the configuration or technical definition of a paginated application role list record.
            * **Interpretation:** The provider supplies `pagingCallback` as configuration or technical metadata on `PaginatedApplicationRoleList`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-applicationroles-size-e4013eb4b02f" title="Size" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.size`

            Size reports the number of application roles returned in the current page. It records page occupancy for the paginated collection.

            * **Enables:** verify page boundaries and distinguish a short or empty role page from the configured maximum.
            * **Interpretation:** The provider supplies `size` as an integer item count, not bytes; zero denotes an empty page while missing means page size was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-apptype-39ffa68bdffa" title="App Type" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `users.appType`

            App Type states app account subtype when `accountType` is app (service, agent, or unknown). It preserves the provider's current classification of this record.

            * **Enables:** separate user records by the exact provider-reported app type value when describing their recorded state.
            * **Interpretation:** The provider supplies `appType` per jira cloud user record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, app type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-avatarurls-fb5ceedac93b" title="Avatar URLs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.avatarUrls`

            Avatar URLs records URLs for the user's avatar images in various sizes. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-users-avatarurls-16x16-fc3e66cbf7b0" title="16x16" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.avatarUrls.16x16`

            16x16 records URL for the 16x16 pixel avatar image. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-users-avatarurls-24x24-9f2002390927" title="24x24" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.avatarUrls.24x24`

            24x24 records URL for the 24x24 pixel avatar image. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-users-avatarurls-32x32-c6b0898f22d6" title="32x32" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.avatarUrls.32x32`

            32x32 records URL for the 32x32 pixel avatar image. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-users-avatarurls-48x48-7dc4bca31b6e" title="48x48" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.avatarUrls.48x48`

            48x48 records URL for the 48x48 pixel avatar image. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-users-displayname-1f898c309a13" title="Display Name" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.displayName`

            Display Name records user's display name as shown in the Jira UI. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira cloud user record to the provider-reported person or account represented by display name.
            * **Interpretation:** The provider supplies `displayName` as identity or attribution context on each jira cloud user record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-emailaddress-862ec5b99aa0" title="Email Address" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.emailAddress`

            Email Address records user's email address. May be absent if hidden by the user's privacy settings. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira cloud user record to the provider-reported person or account represented by email address.
            * **Interpretation:** The provider supplies `emailAddress` as identity or attribution context on each jira cloud user record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-expand-3da7d11fad9b" title="Expand" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `users.expand`

            Expand records comma-separated list of expanded properties included in this response. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact expand when validating the configuration or technical definition of a jira cloud user record.
            * **Interpretation:** The provider supplies `expand` as configuration or technical metadata on `JiraCloudUser`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-groups-85c0cb76e000" title="Groups" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups`

            Groups records groups the user belongs to. Only present when expanded. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira cloud user record with the specific provider container named by groups.
            * **Interpretation:** The provider returns `groups` as a nested object or reference on `JiraCloudUser`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-groups-callback-52da0758309a" title="Callback" icon="phone" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.callback`

            Callback records callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact callback when validating the configuration or technical definition of a paginated group list record.
            * **Interpretation:** The provider supplies `callback` as configuration or technical metadata on `PaginatedGroupList`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-groups-items-28b140bf03b1" title="Items" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.items`

            Items captures the list of group items. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** enumerate the nested items records contained by each paginated group list record.
            * **Interpretation:** The provider returns `items` as a list on `PaginatedGroupList`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-groups-items-groupid-6d3684e96586" title="Group ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.items.groupId`

            Group ID captures the unique identifier of the group. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiracloud-users-groups-items-name-235dbc5b0cc1" title="Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.items.name`

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

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

          <Accordion id="provider-permission-field-jiracloud-users-groups-items-self-ce255e8e061b" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.items.self`

            Self records REST API URL for this group resource. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiracloud-users-groups-max-results-abaf560dd38c" title="Max Results" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.max-results`

            Max Results reports maximum number of results per page. It preserves the stated measure at this record's granularity.

            * **Enables:** measure the provider-reported max results for each paginated group list record.
            * **Interpretation:** The provider supplies `max-results` at paginated group list granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-groups-pagingcallback-e104c1a021e9" title="Paging Callback" icon="headset" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.pagingCallback`

            Paging Callback records paging callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

            * **Enables:** inspect the exact paging callback when validating the configuration or technical definition of a paginated group list record.
            * **Interpretation:** The provider supplies `pagingCallback` as configuration or technical metadata on `PaginatedGroupList`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-groups-size-173ba3120b83" title="Size" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.size`

            Size reports the number of groups returned in the current page. It records page occupancy for the paginated collection.

            * **Enables:** verify page boundaries and distinguish a short or empty group page from the configured maximum.
            * **Interpretation:** The provider supplies `size` as an integer item count, not bytes; zero denotes an empty page while missing means page size was not reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-locale-b6e44c1c3ede" title="Locale" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `users.locale`

            Locale records user's locale setting as a BCP 47 language tag (e.g., `en_US`). It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for users using the recorded locale.
            * **Interpretation:** The provider supplies `locale` as location or localization context per jira cloud user record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-self-dbf35e58fd7b" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.self`

            Self records REST API URL for this 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 jira cloud user record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira cloud user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiracloud-users-timezone-9a98066494e4" title="Time Zone" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.timeZone`

            Time Zone records user's configured IANA timezone (e.g., America/`New_York`). It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

            * **Enables:** interpret dates, times, or localized text for users using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per jira cloud user record; it does not establish a person's real-time physical location.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    * [Jira Cloud REST API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/)
    * [Atlassian service account OAuth credentials](https://support.atlassian.com/user-management/docs/create-oauth-2-0-credential-for-service-accounts/)
    * [Jira OAuth scopes](https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/)
  </Tab>
</Tabs>