> ## 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 Data Center

> Sync issues, projects, and users from Jira Data Center (self-hosted). Issue changelogs are embedded via expand=changelog on the issues tap.

Sync issues, projects, and users from Jira Data Center (self-hosted). Issue changelogs are embedded via expand=changelog on the issues tap.

<Tabs>
  <Tab title="Overview">
    Connect Parable to Jira Server or Data Center using Personal Access Tokens (PATs) for secure API access without exposing passwords.

    | Feature     | Jira Server  | Jira Cloud        |
    | ----------- | ------------ | ----------------- |
    | API Version | v2           | v2 and v3         |
    | Auth        | PAT or Basic | API Token + Basic |
    | Base URL    | Custom       | `*.atlassian.net` |
    | Audit Logs  | Limited      | Full              |

    > **Tip:** **Rate Limits:** Jira Server enforces rate limits of **varies by server configuration**.
    >
    > Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

    ## Data streams

    This Provider Plugin defines 3 data streams.

    | Stream     | Description                                                                   | Sync        |
    | ---------- | ----------------------------------------------------------------------------- | ----------- |
    | `projects` | Jira Data Center projects                                                     | full        |
    | `users`    | Jira Data Center users                                                        | full        |
    | `issues`   | Jira Data Center issues via JQL search (v2 API, includes embedded changelogs) | incremental |
  </Tab>

  <Tab title="Setup Guide">
    ### Personal access token

    #### What You'll Need

    | Credential                | What it is                  |
    | ------------------------- | --------------------------- |
    | **Username**              | Jira account username       |
    | **Personal Access Token** | Generated from Jira profile |
    | **Base URL**              | Your Jira Server URL        |

    > **Info:** **Setup access in Jira Server.** These steps require **Administrator**, or a colleague with equivalent permissions who can create credentials for you.
    >
    > If that is not you, ask your Jira Server administrator.

    * **Jira Administrator** or user with Browse Projects permission
    * Personal Access Tokens enabled on your instance (Jira 8.14+)
    * Network access to your Jira Server

    #### Step 1: Access Profile Settings

    1. Log in to your Jira Server instance
    2. Click your avatar → **Profile**
    3. Navigate to **Personal Access Tokens**

    > **Info:** PATs require Jira Server 8.14 or later. For older versions, use Basic Auth with username/password.

    #### Step 2: Create Personal Access Token

    1. Click **Create token**
    2. Enter name: `Parable Integration`
    3. Set expiration (optional)
    4. Click **Create**

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

    #### Step 3: Note Your Base URL

    Your Jira Server URL format:

    ```
    https://jira.yourcompany.com
    ```

    #### Step 4: Enter values in the form

    1. Enter **Username**, **Personal Access Token**, and **Base URL** in the Provider form.
    2. Click **Save & test connection**.

    ```bash With Personal Access Token theme={null}
    curl -H "Authorization: Bearer YOUR_TOKEN" \
      "https://jira.yourcompany.com/rest/api/2/myself"
    ```

    ```bash With Basic Auth (older versions) theme={null}
    curl -u "username:password" \
      "https://jira.yourcompany.com/rest/api/2/myself"
    ```

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

  <Tab title="Permissions">
    <AccordionGroup>
      <Accordion id="provider-permission-tap-jiradatacenter-issues-24594713d28b" title="Issues" icon="diagram-project" iconType="sharp-duotone-solid">
        Developer identifier: `issues`

        Issues contain Jira Data Center issues via JQL search (v2 API, includes embedded changelogs).

        * **Enables:** report issue content, state, assignment, and embedded change history as work-record context.
        * **Scope:** Reads provider changes through `POST /rest/api/2/search` 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-jiradatacenter-issues-changelog-3558004ba888" title="Changelog" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog`

            Changelog records change history for the issue (present when `expand=changelog`). It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-8b51327c8a4f" title="Histories" icon="badge-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 record.
            * **Interpretation:** The provider returns `histories` as a list on `Changelog`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-3d5d9d727a68" title="Author" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author`

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

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

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

            Account ID is the unique account ID (Atlassian account ID, if applicable). 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 `User`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-c0b44a1141cd" 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 record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-675e2518812b" title="Avatar URLs" icon="lock" 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 record.
            * **Interpretation:** The provider supplies `avatarUrls` as a URL or resource locator on each user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-fd12c72f354c" title="16x16" icon="badge-check" 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-jiradatacenter-issues-changelog-histories-author-31e65f7e6680" title="24x24" icon="unlock" 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-jiradatacenter-issues-changelog-histories-author-27ae7038862c" title="32x32" icon="user-shield" 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-jiradatacenter-issues-changelog-histories-author-8d05e13e8c7b" title="48x48" icon="shield-check" 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-jiradatacenter-issues-changelog-histories-author-4e0392b7dafd" title="Display Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.displayName`

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

            * **Enables:** attribute the 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 user record. In Jira Data Center, 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-jiradatacenter-issues-changelog-histories-author-76eefcca9812" title="Email Address" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.emailAddress`

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

            * **Enables:** attribute the 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 user record. In Jira Data Center, 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-jiradatacenter-issues-changelog-histories-author-7958d58da870" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.key`

            Key identifies user key (unique identifier in Jira Data Center). 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 `User`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-86a53fe0ed5d" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.author.name`

            Name records username / login name. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-6b0e5202859a" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-author-467d30ac8b6f" title="Time Zone" icon="location-crosshairs" 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 record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-create-c24b050c2d65" title="Created" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.created`

            Created records the timestamp when the change was 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 change 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-jiradatacenter-issues-changelog-histories-id-ea413469f4b7" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.id`

            ID is the unique ID of the history 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 `ChangeHistory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-items-29db010f62f1" title="Items" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-items--64015af3afa6" title="Field" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.field`

            Field records human-readable 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 change item record.
            * **Interpretation:** The provider supplies `field` at change item granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

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

            Field ID identifies machine ID of the field (e.g., status, `customfield_10001`). 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 `ChangeItem`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-histories-items--c55e3208baeb" 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-jiradatacenter-issues-changelog-histories-items--53f5b5ebcfa9" title="From" icon="circle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.from`

            From records previous value ID/key (for reference fields). 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-jiradatacenter-issues-changelog-histories-items--6bf880777f33" title="From String" icon="circle-info" 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-jiradatacenter-issues-changelog-histories-items--f77be204a6b4" title="To" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `issues.changelog.histories.items.to`

            To records new value ID/key (for reference fields). 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-jiradatacenter-issues-changelog-histories-items--392e284ba598" title="To String" icon="circle-info" 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-jiradatacenter-issues-changelog-maxresults-ffdf0bd5988d" 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 record.
            * **Interpretation:** The provider supplies `maxResults` at changelog granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

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

            Start At identifies the zero-based 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 pagination metadata, not a history count or business measure; zero denotes the first page.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-changelog-total-30b5060aadd4" title="Total" icon="map-location-dot" 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 record.
            * **Interpretation:** The provider supplies `total` at changelog granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-expand-5f6997a4882b" 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 data center issue record.
            * **Interpretation:** The provider supplies `expand` as configuration or technical metadata on `JiraDataCenterIssue`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-77febfe9aae6" title="Fields" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields`

            Fields records all standard and custom fields on 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-jiradatacenter-issues-fields-aggregateprogress-b73ac4df3fb3" title="Aggregateprogress" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress`

            Aggregateprogress groups time spent, the original estimate, 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 object whose time values are seconds and whose percent value expresses completion; absence means no rollup was reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-aggregateprogress-p-ba6a18302015" title="Percent" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress.percent`

            Percent reports the issue's completion percentage. It summarizes the relationship between time spent and the original 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-jiradatacenter-issues-fields-aggregateprogress-p-e2fd197e3f15" title="Progress" icon="stopwatch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress.progress`

            Progress reports progress value (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 record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-aggregateprogress-t-0fa5237c59d7" title="Total" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.aggregateprogress.total`

            Total reports the total value (original estimate 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 record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-aggregatetimeestima-3c007f8e05bb" title="Aggregatetimeestimate" icon="calendar-clock" 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-jiradatacenter-issues-fields-aggregatetimeorigin-2000f3757866" title="Aggregatetimeoriginalestimate" icon="calendar-days" 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-jiradatacenter-issues-fields-aggregatetimespent-53a4387371df" title="Aggregatetimespent" icon="stopwatch" 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-jiradatacenter-issues-fields-assignee-20747624bcdb" title="Assignee" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.assignee`

            Assignee records user currently assigned to the 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 Data Center, assignee is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-attachment-0f3e8d0f5b76" title="Attachment" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment`

            Attachment records file attachments on the 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-jiradatacenter-issues-fields-attachment-author-0c4ba167f8e8" title="Author" icon="badge-check" 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 record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each attachment record. In Jira Data Center, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-attachment-content-a14cb3a74764" title="Content" icon="user-shield" 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 record.
            * **Interpretation:** The provider supplies `content` at attachment granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-attachment-created-ac52812c4706" title="Created" icon="globe" 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 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-jiradatacenter-issues-fields-attachment-filename-731204934e8d" title="Filename" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.filename`

            Filename records original filename of the attachment. It keeps the exact text, label, or authored value needed to interpret the record.

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

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

            ID is the unique ID of 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 `Attachment`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-attachment-mimetype-5d57d87662e1" 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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, MIME type is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-attachment-self-99cfde232ab4" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each attachment record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-attachment-size-1065b208a936" title="Size" icon="unlock" 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-jiradatacenter-issues-fields-attachment-thumbnai-fa9748e7744f" title="Thumbnail" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.attachment.thumbnail`

            Thumbnail records URL of the attachment thumbnail (if applicable). It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-closedsprints-5db4017ae769" title="Closed Sprints" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints`

            Closed Sprints records completed sprints the 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-jiradatacenter-issues-fields-closedsprints-compl-e29dac818323" title="Completion Date" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.completeDate`

            Completion Date records completion date/time of the sprint. 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 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-jiradatacenter-issues-fields-closedsprints-endda-8c353ab3a31f" title="End Date" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.endDate`

            End Date records end date/time 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 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-jiradatacenter-issues-fields-closedsprints-goal-9b016359c8f6" title="Goal" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.goal`

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

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

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

            ID is the unique ID of 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 `Sprint`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-closedsprints-name-9219b7119933" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.name`

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-closedsprints-origi-e47fd097eaa3" title="Origin Board ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.originBoardId`

            Origin Board ID is the ID of the board the sprint originated from. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-closedsprints-self-b48f9a9aa038" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each sprint record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-closedsprints-start-6da9766e9428" title="Start Date" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.startDate`

            Start Date records start date/time 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 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-jiradatacenter-issues-fields-closedsprints-state-2ff1fe2e9ead" title="State" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.closedSprints.state`

            State states state of the sprint (future, active, closed). 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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, state is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-45a0d189453d" title="Comment" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment`

            Comment records comments on the 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-jiradatacenter-issues-fields-comment-comments-3f09debd93f7" title="Comments" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments`

            Comments records list of comments. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-au-964a074c8b24" title="Author" icon="badge-check" 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 record to the provider-reported actor represented by author.
            * **Interpretation:** The provider supplies `author` as identity or attribution context on each comment record. In Jira Data Center, author is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-bo-0b70b5c047a6" title="Body" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.body`

            Body records comment body text. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-cr-d798681c297e" title="Created" icon="globe" 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 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-jiradatacenter-issues-fields-comment-comments-id-99146454b4dc" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.id`

            ID is the unique ID of 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 `Comment`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-se-c56f69827a99" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each comment record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-up-567e33a8002e" title="Update Author" icon="lock" 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 record to the provider-reported actor represented by update author.
            * **Interpretation:** The provider supplies `updateAuthor` as identity or attribution context on each comment record. In Jira Data Center, 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-jiradatacenter-issues-fields-comment-comments-up-a422f31b2442" title="Updated" icon="earth-americas" 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 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-jiradatacenter-issues-fields-comment-comments-vi-165470e29a70" title="Visibility" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.comments.visibility`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-vi-e441ad9bfb14" 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 record.
            * **Interpretation:** The provider supplies `type` at visibility granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Data Center, type is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-comments-vi-8b2a46d93232" title="Value" icon="unlock" 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-jiradatacenter-issues-fields-comment-maxresults-67aec1d99289" 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-jiradatacenter-issues-fields-comment-startat-f8a9aa3c3732" title="Start At" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.comment.startAt`

            Start At identifies the zero-based 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 pagination metadata, not a comment count or business measure; zero denotes the first page.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-comment-total-38f34950673a" title="Total" icon="map-location-dot" 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-jiradatacenter-issues-fields-components-641220ae8e67" title="Components" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components`

            Components records components associated with the 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-jiradatacenter-issues-fields-components-assignee-ca94104f9e21" title="Assignee Type" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.assigneeType`

            Assignee Type states default assignee type for the component. It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-components-descript-5d61a98879f5" title="Description" icon="user-shield" 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 record.
            * **Interpretation:** The provider supplies `description` at component granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

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

            ID is the unique ID of 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 `Component`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-components-lead-b2f3b787c95c" title="Lead" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.lead`

            Lead records component lead user. It keeps the provider-reported person or account context attached to the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-components-name-7c6292f4432f" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.components.name`

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-components-self-4d9e82365d5f" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each component record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-created-f78298800b03" title="Created" icon="globe" 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-jiradatacenter-issues-fields-creator-701ba6e8ec8d" title="Creator" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.creator`

            Creator records user who originally created the issue record. 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 Data Center, creator is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-customfields-1c23bb4499b1" title="Custom Fields" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.customFields`

            Custom Fields records arbitrary custom fields (`customfield_NNNNN`) not explicitly modeled. It retains configured attributes whose keys or shape are not fixed by this base schema.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-description-052853dc4273" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.description`

            Description records full description body of the issue (wiki markup 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 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-jiradatacenter-issues-fields-duedate-4999186f2c66" 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-jiradatacenter-issues-fields-environment-36a002ad2acc" title="Environment" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.environment`

            Environment states environment information for the issue. 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 Data Center, environment is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-epic-c80cd1c6eaae" title="Epic" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic`

            Epic records epic this issue belongs to (Jira Software). 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-jiradatacenter-issues-fields-epic-color-aaad857f2ff0" title="Color" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.color`

            Color records color configuration of the epic. It preserves the provider's visual treatment for the represented object.

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

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

            Key identifies color key identifier (e.g., `color_1`, `color_2`). 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 `EpicColor`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-epic-done-11075810c190" title="Done" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.done`

            Done indicates whether the epic is marked as done. It preserves the provider-reported yes-or-no condition for this record.

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

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

            ID is the unique ID of the epic. 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 `EpicReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

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

            Key identifies issue key of the epic. 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 `EpicReference`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-epic-name-a82bcd78cc43" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.epic.name`

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

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

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

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

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

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

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

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

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

            Fix Versions records fix versions associated with the 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-jiradatacenter-issues-fields-fixversions-archive-3f35b8278c45" title="Archived" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.archived`

            Archived indicates whether the 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 record; false and missing are distinct when the field is optional. In Jira Data Center, archived is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-fixversions-descrip-c4692f305f74" title="Description" icon="user-shield" 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 record.
            * **Interpretation:** The provider supplies `description` at version granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

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

            ID is the unique ID of 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 `Version`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-fixversions-name-2a4ef1b33972" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.name`

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-fixversions-release-fecb28fd4cc2" title="Released" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.released`

            Released indicates whether the 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 record; false and missing are distinct when the field is optional. In Jira Data Center, released is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-fixversions-release-d85f2b5ab56e" title="Release Date" icon="globe" 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 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-jiradatacenter-issues-fields-fixversions-self-7af48491879a" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each version record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-fixversions-startda-e73957a2cc09" title="Start Date" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.fixVersions.startDate`

            Start Date records start date of the version. 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 version 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-jiradatacenter-issues-fields-flagged-a6b2b651bfef" title="Flagged" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.flagged`

            Flagged indicates whether the issue is flagged/impediment. It preserves the provider-reported yes-or-no condition for this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-a701f0b47d0e" title="Issuelinks" icon="lock" 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-jiradatacenter-issues-fields-issuelinks-id-aa503a96d82d" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.id`

            ID is the unique ID of 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 `IssueLink`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-5876d184a040" title="Inward Issue" icon="badge-check" 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 record.
            * **Interpretation:** The provider returns `inwardIssue` as a nested object or reference on `IssueLink`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-0f235c1476ec" title="Fields" icon="percent" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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-jiradatacenter-issues-fields-issuelinks-inwardis-97a6f8c3d371" title="Issuetype" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 Data Center, issuetype is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-cc87c9b1ef35" title="Avatar ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.issuetype.avatarId`

            Avatar ID identifies avatar ID 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 avatar ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `avatarId` as a record-level identifier on `IssueType`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-7df1da546210" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `description` at issue type granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-011d9fe8e8e4" title="Icon URL" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `iconUrl` as a URL or resource locator on each issue type record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-2141dffb7cb3" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.issuetype.id`

            ID is the unique ID of 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 `IssueType`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-5642cb6984ca" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.issuetype.name`

            Name states display name (e.g., Bug, Story, Task, Epic, Sub-task). It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-baaca539e724" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each issue type record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-f706235d6d25" title="Subtask" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.issuetype.subtask`

            Subtask indicates whether this issue type represents a subtask. 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 record; false and missing are distinct when the field is optional. In Jira Data Center, subtask is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-0f1addbdea94" title="Priority" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 Data Center, priority is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-9713bfdbf411" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.priority.description`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-7a0fcf2d31b6" title="Icon URL" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `iconUrl` as a URL or resource locator on each priority record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-8d68b5061e52" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.priority.id`

            ID is the unique ID of 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 `Priority`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-3efa73ca28d5" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.priority.name`

            Name states display name of the priority (e.g., Highest, High, Medium, Low, Lowest). It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-f795dba47fbc" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each priority record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-c301db61088a" title="Status" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 Data Center, status is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-acdeb979be07" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `description` at status granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-de519a497649" title="Icon URL" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `iconUrl` as a URL or resource locator on each status record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-6282f32c1a16" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.status.id`

            ID is the unique ID of 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 `Status`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-d93ce9aff126" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 Data Center status name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per status record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-44fa9a1d5588" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each status record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-6af5e9b22351" title="Status Category" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.status.statusCategory`

            Status Category states high-level category of the 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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, status category is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-d827b289dc2f" title="Color Name" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.status.statusCategory.colorName`

            Color Name records color name 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-jiradatacenter-issues-fields-issuelinks-inwardis-8d2cf1d6950b" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.status.statusCategory.id`

            ID is the unique ID 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 ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `StatusCategory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-93a05801ee41" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.fields.status.statusCategory.key`

            Key is the key of the status category (e.g., new, indeterminate, done). 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 `StatusCategory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-175749cc4222" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 Data Center status category name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per status category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-84ccae36bd8e" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each status category record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-inwardis-32c3979dd2de" title="Summary" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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-jiradatacenter-issues-fields-issuelinks-inwardis-86c0beea0c29" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.id`

            ID is the unique numeric ID 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-jiradatacenter-issues-fields-issuelinks-inwardis-6f1453e71d99" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.key`

            Key identifies human-readable issue key. 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-jiradatacenter-issues-fields-issuelinks-inwardis-5367f5322a3c" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.inwardIssue.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-jiradatacenter-issues-fields-issuelinks-outwardi-5baa26deb07c" title="Outward Issue" icon="lock" 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 record.
            * **Interpretation:** The provider returns `outwardIssue` as a nested object or reference on `IssueLink`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-type-7a29f3ac79ec" title="Type" icon="map-location-dot" 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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, type is the work record's classification, not an individual-performance measure.
          </Accordion>

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

            ID is the unique ID of 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 `IssueLinkType`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-type-inw-b1b2ef982a80" title="Inward" icon="passport" 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 record.
            * **Interpretation:** The provider supplies `inward` at issue link type granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-type-nam-d9de1f815f9c" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuelinks.type.name`

            Name records name of the link type (e.g., Blocks, Cloners, Duplicate). 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 record.
            * **Interpretation:** The provider supplies `name` at issue link type granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-type-out-11ac0e6cf7e0" title="Outward" icon="shield-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 record.
            * **Interpretation:** The provider supplies `outward` at issue link type granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuelinks-type-sel-7cdc5a41c647" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each issue link type record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-issuetype-adbd4d120def" title="Issuetype" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.issuetype`

            Issuetype states type of issue (Bug, Story, Task, Epic, 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 Data Center, issuetype is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-labels-a71c6fd5188d" title="Labels" icon="shield-check" 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-jiradatacenter-issues-fields-lastviewed-fe56cd1cb303" 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-jiradatacenter-issues-fields-parent-aafac172b499" title="Parent" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.parent`

            Parent records parent issue reference (for subtasks or child issues). 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-jiradatacenter-issues-fields-priority-03c324e2167f" 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 Data Center, priority is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-progress-850f74a03976" title="Progress" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.progress`

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

            * **Enables:** compare spent time with the issue estimate and identify incomplete or overrunning work.
            * **Interpretation:** The provider supplies `progress` as a nested object whose time values are seconds and whose percent value expresses completion; absence means no issue progress was reported.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-756da03864e7" title="Project" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project`

            Project records project the 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-jiradatacenter-issues-fields-project-avatarurls-88dc1df6458a" title="Avatar URLs" icon="lock" 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 record.
            * **Interpretation:** The provider supplies `avatarUrls` as a URL or resource locator on each project record. Availability still follows the provider's permissions and retention.
          </Accordion>

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

            ID is the unique ID of 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 `Project`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

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

            Key identifies project key (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 `Project`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-name-da7b44a546d2" title="Name" icon="lock" 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 record.
            * **Interpretation:** The provider supplies `name` at project granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-projectcate-795f8f54c304" title="Project Category" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory`

            Project Category states category the project belongs to. 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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, project category is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-projectcate-bcc025f6b9d9" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.description`

            Description records description of the 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-jiradatacenter-issues-fields-project-projectcate-583550c21191" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.id`

            ID is the unique ID of 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 `ProjectCategory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-projectcate-0812b721ed3f" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.name`

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

            * **Enables:** filter and group issue records by the Jira Data Center 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 Data Center, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-projectcate-07eedbe51977" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectCategory.self`

            Self records REST API URL for this project 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 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-jiradatacenter-issues-fields-project-projecttype-66dc23fea7e9" title="Project Type Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.project.projectTypeKey`

            Project Type Key identifies project type key (e.g., 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 `Project`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-project-self-fdf00f87cff6" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each project record. Availability still follows the provider's permissions and retention.
          </Accordion>

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

            Reporter records user who created the 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 Data Center, reporter is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-resolution-a6d26d28ea26" title="Resolution" icon="earth-americas" 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 Data Center, resolution is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-resolution-descript-556807f51bcd" title="Description" icon="user-shield" 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 record.
            * **Interpretation:** The provider supplies `description` at resolution granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

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

            ID is the unique ID of 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 `Resolution`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-resolution-name-d053ab9f85ad" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.resolution.name`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-resolution-self-629563582a4c" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each resolution record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-resolutiondate-2af2101d9705" title="Resolutiondate" icon="globe" 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-jiradatacenter-issues-fields-security-a7f16d83a756" title="Security" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security`

            Security states security level of the 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 Data Center, security is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-security-descriptio-c7adfc3312dd" title="Description" icon="user-shield" 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 record.
            * **Interpretation:** The provider supplies `description` at security level granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-security-id-752b56d13f04" title="ID" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security.id`

            ID is the unique ID of 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 `SecurityLevel`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-security-name-b53125ac596e" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.security.name`

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-security-self-fd29ae1c3849" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each security level record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-sprint-8477b6fbbbed" title="Sprint" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.sprint`

            Sprint states active sprint the issue is in (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 Data Center, sprint is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-status-bd45866cdf97" 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 Data Center, status is the work record's classification, not an individual-performance measure.
          </Accordion>

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

            Statuscategorychangedate records the timestamp when the issue's status category most recently 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-jiradatacenter-issues-fields-storypoints-caf82453cfec" title="Story Points" icon="ranking-star" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.storyPoints`

            Story Points records story point 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-jiradatacenter-issues-fields-subtasks-afd57b0bcbc2" title="Subtasks" icon="badge-check" 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-jiradatacenter-issues-fields-summary-5357888a4939" title="Summary" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.summary`

            Summary records one-line summary/title of 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-jiradatacenter-issues-fields-timeestimate-8a4850be693b" title="Timeestimate" icon="clock-rotate-left" 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-jiradatacenter-issues-fields-timeoriginalestimat-04636c007838" title="Timeoriginalestimate" icon="clock-rotate-left" 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-jiradatacenter-issues-fields-timespent-92560d26d2c5" 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-jiradatacenter-issues-fields-timetracking-b1e277f85b56" 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-jiradatacenter-issues-fields-timetracking-origin-1f1903590dd0" title="Original Estimate" icon="calendar-days" 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 `2d 4h`; consumers must use Jira's unit conventions rather than treat the string as an ordinal.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-timetracking-origin-8c515fbc2313" title="Original Estimate Seconds" icon="calendar-clock" 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 record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-timetracking-remain-29ab1d19f065" title="Remaining Estimate" icon="stopwatch" 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-jiradatacenter-issues-fields-timetracking-remain-d287833c6895" title="Remaining Estimate Seconds" icon="stopwatch" 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 record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-timetracking-timesp-fe15ae59ac10" title="Time Spent" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.timeSpent`

            Time Spent reports human-readable 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 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-jiradatacenter-issues-fields-timetracking-timesp-53136c4202f0" title="Time Spent Seconds" icon="clock-rotate-left" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.timetracking.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 time tracking record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-updated-f6899cd7c0e4" title="Updated" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.updated`

            Updated records the timestamp of the last modification to the issue. 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-jiradatacenter-issues-fields-versions-7617561c38a8" title="Versions" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.versions`

            Versions records affects versions associated with the 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-jiradatacenter-issues-fields-votes-d90705b383e2" title="Votes" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.votes`

            Votes records vote count and self-vote status. It retains the exact provider location for the referenced resource.

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

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

            Has Voted indicates whether the current user has voted for this issue. 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 vote record; false and missing are distinct when the field is optional. In Jira Data Center, has voted is a condition on the work record, not an individual-performance measure.
          </Accordion>

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-votes-votes-3f8fcaddf770" title="Votes" icon="location-crosshairs" 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 vote record.
            * **Interpretation:** The provider supplies `votes` at vote granularity as a count at one value per record; zero and missing are not interchangeable.
          </Accordion>

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

            Watches records watch count and self-watch status. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-watches-iswatching-39daf19c0d3f" title="Is Watching" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.watches.isWatching`

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

            * **Enables:** separate issues the current user watches from those they do not.
            * **Interpretation:** The provider supplies `isWatching` as a boolean per watches record; false and missing are distinct. It is a condition on the issue, not an individual-performance measure.
          </Accordion>

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

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-watches-watchcount-9b81ebca4d35" title="Watch Count" icon="ranking-star" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.watches.watchCount`

            Watch Count reports the number of users watching the issue. It preserves the audience count in the watcher summary.

            * **Enables:** compare issue interest using the provider-reported watcher totals.
            * **Interpretation:** The provider supplies `watchCount` as an integer count per watches record; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-9fd263dac6b1" title="Worklog" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog`

            Worklog records worklogs recorded against the 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-jiradatacenter-issues-fields-worklog-maxresults-213a826815e2" 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-jiradatacenter-issues-fields-worklog-startat-ee8655230d3f" title="Start At" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.startAt`

            Start At identifies the zero-based 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 pagination metadata, not a worklog count or business measure; zero denotes the first page.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-total-38de47a53e5c" title="Total" icon="map-location-dot" 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-jiradatacenter-issues-fields-worklog-worklogs-28913b0f8818" title="Worklogs" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs`

            Worklogs records list of worklogs. 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-jiradatacenter-issues-fields-worklog-worklogs-au-bb28fafd5ac6" title="Author" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.author`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-worklogs-co-4a86f56a039d" title="Comment" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.comment`

            Comment records comment on the worklog entry. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-worklogs-cr-cb8fa69b4e2a" title="Created" icon="globe" 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 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-jiradatacenter-issues-fields-worklog-worklogs-id-cf4a7c4349ac" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.id`

            ID is the unique ID of 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 `Worklog`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-worklogs-se-d61df15c82d4" 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 record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each worklog record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-worklogs-st-86f887ae1dd5" title="Started" icon="location-crosshairs" 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 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-jiradatacenter-issues-fields-worklog-worklogs-ti-0b8259cc4fbc" title="Time Spent" icon="globe" 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 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-jiradatacenter-issues-fields-worklog-worklogs-ti-09212344d0b2" title="Time Spent Seconds" icon="clock-rotate-left" 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 record in seconds; it is an elapsed or recorded interval, not an outcome measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-worklog-worklogs-up-fa5bb131a0d7" title="Update Author" icon="lock" 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 record to the provider-reported actor represented by update author.
            * **Interpretation:** The provider supplies `updateAuthor` as identity or attribution context on each worklog record. In Jira Data Center, 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-jiradatacenter-issues-fields-worklog-worklogs-up-560682ae0555" title="Updated" icon="earth-americas" 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 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-jiradatacenter-issues-fields-worklog-worklogs-vi-72d981e4bd8c" title="Visibility" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `issues.fields.worklog.worklogs.visibility`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-issues-fields-workratio-669059376ba4" title="Workratio" icon="chart-column" 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 for which the ratio does not apply.
            * **Interpretation:** The provider supplies `workratio` as an integer percentage and uses `-1` when the ratio is not applicable; `-1`, zero, and missing have different meanings.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-id-1685c47640ea" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `issues.id`

            ID is the unique numeric ID of 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 data center issue source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per jira data center issue record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-key-d1bb505f8464" 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 `JiraDataCenterIssue`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-project-key-4b7ec532cd63" title="Project Key" icon="id-card" 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 `JiraDataCenterIssue`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-issues-self-ad838f4b7e06" 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 data center issue record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira data center issue record. Availability still follows the provider's permissions and retention.
          </Accordion>
        </AccordionGroup>
      </Accordion>

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

        Projects contain Jira Data Center projects.

        * **Enables:** map Jira Data Center issues to their self-hosted project containers.
        * **Scope:** Reads the declared collection through `GET /rest/api/2/project` 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-jiradatacenter-projects-archived-b8b30318bf07" title="Archived" icon="circle-check" 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 data center project record; false and missing are distinct when the field is optional. In Jira Data Center, archived is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-assigneetype-59e0ce209daf" title="Assignee Type" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `projects.assigneeType`

            Assignee Type states default assignee type for the project. It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-avatarurls-636430d8a812" title="Avatar URLs" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira data center project record.
            * **Interpretation:** The provider supplies `avatarUrls` as a URL or resource locator on each jira data center project record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-avatarurls-16x16-03dd23842528" title="16x16" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira avatar url record.
            * **Interpretation:** The provider supplies `16x16` as a URL or resource locator on each jira avatar url record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-avatarurls-24x24-8f6c0e578479" title="24x24" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira avatar url record.
            * **Interpretation:** The provider supplies `24x24` as a URL or resource locator on each jira avatar url record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-avatarurls-32x32-7b340d978c1b" title="32x32" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira avatar url record.
            * **Interpretation:** The provider supplies `32x32` as a URL or resource locator on each jira avatar url record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-avatarurls-48x48-a2c356a93ba0" title="48x48" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira avatar url record.
            * **Interpretation:** The provider supplies `48x48` as a URL or resource locator on each jira avatar url record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-14f287da16ba" title="Components" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components`

            Components records list of components defined in this project. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira data center project record with the specific provider container named by components.
            * **Interpretation:** The provider returns `components` as a list on `JiraDataCenterProject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-708e8c985f33" title="Assignee" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee`

            Assignee records default assignee for the component. It keeps the provider-reported person or account context attached to the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-acti-ee43879117f0" title="Active" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.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 jira user record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-avat-c895a435696b" title="Avatar URLs" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.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 jira user record.
            * **Interpretation:** The provider supplies `avatarUrls` as a URL or resource locator on each jira user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-disp-f5d7d4523408" title="Display Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.displayName`

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

            * **Enables:** attribute the jira 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 user record. In Jira Data Center, 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-jiradatacenter-projects-components-assignee-emai-0e6f5b4381e6" title="Email Address" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.emailAddress`

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

            * **Enables:** attribute the jira 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 user record. In Jira Data Center, 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-jiradatacenter-projects-components-assignee-key-4f09a77883ba" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.key`

            Key is the unique key identifying the user (often the username in Data Center). It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-loca-23020d7be8ef" title="Locale" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.locale`

            Locale records locale preference 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 locale.
            * **Interpretation:** The provider supplies `locale` as location or localization context per jira user record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-name-8a863a88d1b7" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.name`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-self-928c58dad3d0" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.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 user record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assignee-time-3b60f731c117" title="Time Zone" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assignee.timeZone`

            Time Zone records IANA timezone 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 jira user record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-assigneetype-734f429eab7e" title="Assignee Type" icon="earth-americas" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.assigneeType`

            Assignee Type states default assignee type for the component. It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-description-220facf820fc" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira component record.
            * **Interpretation:** The provider supplies `description` at jira component granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-id-cd437ebcf643" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.id`

            ID is the unique numeric ID of the component. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-isassigneetyp-8d79be25452e" title="Is Assignee Type Valid" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.isAssigneeTypeValid`

            Is Assignee Type Valid indicates whether the configured assignee type is valid. It preserves the provider-reported yes-or-no condition for this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-lead-6bd2524a8c38" title="Lead" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.lead`

            Lead records user designated as the component lead. It keeps the provider-reported person or account context attached to the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-name-55557043b3e5" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 jira component record.
            * **Interpretation:** The provider supplies `name` at jira component granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-project-d5c8f18630d7" title="Project" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.project`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-projectid-4cbc7c7b3484" title="Project ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.projectId`

            Project ID reports the numeric ID of the project this component belongs to. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-realassignee-4840c313f655" title="Real Assignee" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.realAssignee`

            Real Assignee records actual resolved assignee after applying project defaults. It keeps the provider-reported person or account context attached to the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-realassigneet-fd79e0b6dab9" title="Real Assignee Type" icon="map-location-dot" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.realAssigneeType`

            Real Assignee Type states actual resolved assignee type after applying project defaults. It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-components-self-1deeeada81cc" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.components.self`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-description-c0b1fee2fcde" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.description`

            Description records full description of the project, may contain wiki markup or HTML. It keeps the exact text, label, or authored value needed to interpret the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-email-978ee2911a46" title="Email" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.email`

            Email records email address associated with the project, if configured. It keeps the provider-reported person or account context attached to the record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-entityid-86590004cbf8" title="Entity ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.entityId`

            Entity ID identifies global entity ID for the project, used in cross-product integrations. 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 `JiraDataCenterProject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-expand-68f829bc1a6c" title="Expand" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `projects.expand`

            Expand records comma-separated list of expanded fields included in the 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 data center project record.
            * **Interpretation:** The provider supplies `expand` as configuration or technical metadata on `JiraDataCenterProject`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-id-2b66cfd1c05e" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.id`

            ID is the unique numeric ID of 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 ID, without assuming that this field alone makes every row unique.
            * **Interpretation:** The provider supplies `id` as a record-level identifier on `JiraDataCenterProject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-isprivate-56a38d48b024" title="Is Private" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.isPrivate`

            Is Private indicates whether the project is private. It documents the access-related value reported for this object or membership.

            * **Enables:** describe the provider-reported is private attached to each jira data center project record.
            * **Interpretation:** The provider supplies `isPrivate` at jira data center project granularity. It describes provider-reported context and does not prove effective access beyond the returned record.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-30bd3d88f4a3" title="Issue Types" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes`

            Issue Types records list of issue types available in this project. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira data center project record with the specific provider container named by issue types.
            * **Interpretation:** The provider returns `issueTypes` as a list on `JiraDataCenterProject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-avatarid-73294178cc66" title="Avatar ID" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.avatarId`

            Avatar ID is the ID of the avatar associated with this issue type. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-description-f75f104f40fe" title="Description" icon="user-shield" 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 jira issue type record.
            * **Interpretation:** The provider supplies `description` at jira issue type granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-iconurl-fb95e2d71cfd" title="Icon URL" icon="passport" 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 jira issue type record.
            * **Interpretation:** The provider supplies `iconUrl` as a URL or resource locator on each jira issue type record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-id-b4427bdcdfd2" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.id`

            ID is the unique numeric ID of 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 jira issue type source row before constructing its represented state.
            * **Interpretation:** The provider supplies `id` at one value per jira issue type record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-name-87017e6f980f" title="Name" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.name`

            Name states name of the issue type (e.g., Bug, Story, Task). It preserves the provider's current classification of this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-self-52a7a637bec6" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.self`

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-issuetypes-subtask-215bc609d78c" title="Subtask" icon="triangle-exclamation" iconType="sharp-duotone-solid">
            Developer identifier: `projects.issueTypes.subtask`

            Subtask indicates whether this issue type represents a subtask. 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 jira issue type record; false and missing are distinct when the field is optional. In Jira Data Center, subtask is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-key-0505d6a0c25e" 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 data center project source row before constructing its represented state.
            * **Interpretation:** The provider supplies `key` at one value per jira data center project record, and `x-transformDedupKey` explicitly marks it as the record key.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-lead-ab3c6ed2d0b2" title="Lead" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.lead`

            Lead records user designated as the project lead. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira data center 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 data center project record. In Jira Data Center, lead is attribution or membership context for the work record, not a measure of an individual's performance.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-name-789184204018" title="Name" icon="lock" 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 data center project record.
            * **Interpretation:** The provider supplies `name` at jira data center project granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-projectcategory-b7df16957463" title="Project Category" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory`

            Project Category states administrative category grouping for the 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 data center project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, project category is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-projectcategory-descript-4f9a9fdf176b" title="Description" icon="user-shield" 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 jira project category record.
            * **Interpretation:** The provider supplies `description` at jira project category granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-projectcategory-id-4e9b276e4382" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectCategory.id`

            ID is the unique numeric ID of 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 `JiraProjectCategory`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-projectcategory-name-ab1f5f5ccb3e" title="Name" icon="globe" 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 Data Center jira project category name exposed by the nested object.
            * **Interpretation:** The provider supplies `name` per jira project category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, name is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-projectcategory-self-2c89acfb6340" 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 jira project category record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira project category record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-projectkeys-bbdab4884d7c" title="Project Keys" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.projectKeys`

            Project Keys records all project keys associated with this project, including historical keys. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-projecttypekey-94f08697347b" title="Project Type Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.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 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 `JiraDataCenterProject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-properties-785a8ea06823" title="Properties" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.properties`

            Properties records arbitrary project properties as key-value pairs. 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-jiradatacenter-projects-roles-9f59b83b6725" title="Roles" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.roles`

            Roles states map of project role names to their REST API URLs. It documents the access-related value reported for this object or membership.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-self-a2b16cd1fed3" 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 data center project record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira data center project record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-simplified-755776199b78" title="Simplified" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `projects.simplified`

            Simplified indicates whether this project uses the simplified project experience. 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 data center project record; false and missing are distinct when the field is optional. In Jira Data Center, simplified is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-style-608dad882b32" title="Style" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.style`

            Style states project style indicator (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 data center project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, style is the work record's classification, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-url-bb0d6e8f1c2b" title="URL" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.url`

            URL records URL associated with the project (may be an external or internal link). It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-uuid-0979f444a520" title="UUID" icon="address-book" iconType="sharp-duotone-solid">
            Developer identifier: `projects.uuid`

            UUID identifies UUID of the project if available. 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 `JiraDataCenterProject`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-2643921649fd" title="Versions" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions`

            Versions records list of versions (releases) defined in this project. It preserves the containing or referenced object needed to reconstruct the provider relationship.

            * **Enables:** associate each jira data center project record with the specific provider container named by versions.
            * **Interpretation:** The provider returns `versions` as a list on `JiraDataCenterProject`; an absent value does not prove that no related object exists outside the credential's visibility.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-archived-b93f623a2bad" title="Archived" icon="circle-check" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.archived`

            Archived indicates whether this version 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 version record; false and missing are distinct when the field is optional. In Jira Data Center, archived is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-description-61b63c04ddba" title="Description" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.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 jira version record.
            * **Interpretation:** The provider supplies `description` at jira version granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-id-d29d98ca5380" title="ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.id`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-name-01a0a03681bc" title="Name" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.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 jira version record.
            * **Interpretation:** The provider supplies `name` at jira version granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-overdue-efbb213275f7" title="Overdue" icon="calendar-days" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.overdue`

            Overdue indicates whether this version is past its release date without being released. It preserves the provider-reported yes-or-no condition for this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-projectid-7b6123a04af1" title="Project ID" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.projectId`

            Project ID reports the numeric ID of the project this version belongs to. It is needed to resolve references that repeat the same provider identifier.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-released-088325860e59" title="Released" icon="code-branch" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.released`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-releasedate-3628e5125c95" title="Release Date" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.releaseDate`

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

            * **Enables:** place project records on a timeline by release date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `releaseDate` per jira version 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-jiradatacenter-projects-versions-self-ef84bc40f213" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.self`

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

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-startdate-f9f2558027b1" title="Start Date" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.startDate`

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

            * **Enables:** place project records on a timeline by start date and select the records within an explicit reporting window.
            * **Interpretation:** The provider supplies `startDate` per jira version 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-jiradatacenter-projects-versions-userreleasedate-6dc8b98679ad" title="User Release Date" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.userReleaseDate`

            User Release Date records user-formatted release date string. It anchors the named event or boundary on the record's timeline.

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

          <Accordion id="provider-permission-field-jiradatacenter-projects-versions-userstartdate-6c0f548f3ef4" title="User Start Date" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `projects.versions.userStartDate`

            User Start Date records user-formatted start date string. It anchors the named event or boundary on the record's timeline.

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

      <Accordion id="provider-permission-tap-jiradatacenter-users-1202663682de" title="Users" icon="address-book" iconType="sharp-duotone-solid">
        Developer identifier: `users`

        Users contain Jira Data Center users.

        * **Enables:** resolve self-hosted Jira identities referenced by issue records.
        * **Scope:** Reads the declared collection through `GET /rest/api/2/user/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-jiradatacenter-users-active-ca6e5182313a" title="Active" icon="circle-info" iconType="sharp-duotone-solid">
            Developer identifier: `users.active`

            Active indicates whether the user account is active. Filters active vs deactivated users for license and adoption analysis. 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 data center user record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-applicationroles-7f3c09b3f921" title="Application Roles" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles`

            Application Roles states application roles assigned to the user (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 data center user record.
            * **Interpretation:** The provider supplies `applicationRoles` at jira data center user granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Data Center, application roles is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-applicationroles-items-75891fb85150" title="Items" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items`

            Items states array of application role objects. It documents the access-related value reported for this object or membership.

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

          <Accordion id="provider-permission-field-jiradatacenter-users-applicationroles-items-key-fa157d038ee6" title="Key" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.key`

            Key captures the key identifier 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 `ApplicationRole`. It is not a uniqueness guarantee unless a connector directive says so.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-applicationroles-items-name-8e83ec6402e6" title="Name" icon="lock" 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 record.
            * **Interpretation:** The provider supplies `name` at application role granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Data Center, name is access or membership context, not an individual-performance measure.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-applicationroles-items-self-10bbe057c3f4" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.items.self`

            Self captures the URL of the application role's REST API resource. It retains the exact provider location for the referenced resource.

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

          <Accordion id="provider-permission-field-jiradatacenter-users-applicationroles-size-a8b4036b775e" title="Size" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.applicationRoles.size`

            Size reports the number of application roles returned in the list. It records collection occupancy for the response.

            * **Enables:** distinguish an empty role collection from one containing the provider-reported number of roles.
            * **Interpretation:** The provider supplies `size` as an integer item count, not bytes; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-avatarurls-ede9a7ebf51d" title="Avatar URLs" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.avatarUrls`

            Avatar URLs records map of 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 jira data center user record.
            * **Interpretation:** The provider supplies `avatarUrls` as a URL or resource locator on each jira data center user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-avatarurls-16x16-1f24f962ebcc" title="16x16" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.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-jiradatacenter-users-avatarurls-24x24-e26b1a43ec93" title="24x24" icon="unlock" iconType="sharp-duotone-solid">
            Developer identifier: `users.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-jiradatacenter-users-avatarurls-32x32-ae5ad770793e" title="32x32" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.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-jiradatacenter-users-avatarurls-48x48-f5b0afa0003b" title="48x48" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.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-jiradatacenter-users-deleted-5c425abff1cb" title="Deleted" icon="calendar-clock" iconType="sharp-duotone-solid">
            Developer identifier: `users.deleted`

            Deleted indicates whether the user account has been deleted. It preserves the provider-reported yes-or-no condition for this record.

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

          <Accordion id="provider-permission-field-jiradatacenter-users-displayname-80a700e0ee60" title="Display Name" icon="shield-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.displayName`

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

            * **Enables:** attribute the jira data center 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 data center user record. In Jira Data Center, 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-jiradatacenter-users-emailaddress-8121ab4282b4" title="Email Address" icon="lock" iconType="sharp-duotone-solid">
            Developer identifier: `users.emailAddress`

            Email Address records email address of the user. Primary cross-connector identity matching key. It keeps the provider-reported person or account context attached to the record.

            * **Enables:** attribute the jira data center 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 data center user record. In Jira Data Center, 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-jiradatacenter-users-expand-1703fd4f3b6d" title="Expand" icon="arrow-trend-down" iconType="sharp-duotone-solid">
            Developer identifier: `users.expand`

            Expand records comma-separated list of expanded properties included in the 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 data center user record.
            * **Interpretation:** The provider supplies `expand` as configuration or technical metadata on `JiraDataCenterUser`; consumers must preserve the exact syntax and documented vocabulary.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-groups-494bffd43ac0" title="Groups" icon="badge-check" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups`

            Groups records groups the user belongs to (when expanded). It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-jiradatacenter-users-groups-items-f96ad717dd07" title="Items" icon="user-shield" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.items`

            Items records array of group objects. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

          <Accordion id="provider-permission-field-jiradatacenter-users-groups-items-name-be467f74e19d" title="Name" icon="lock" 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 record.
            * **Interpretation:** The provider supplies `name` at group granularity in the format stated by its description; omitted or redacted content remains unknown.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-groups-items-self-11b0432a9ef0" title="Self" icon="passport" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.items.self`

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

          <Accordion id="provider-permission-field-jiradatacenter-users-groups-size-7033ccc5d31c" title="Size" icon="arrow-trend-up" iconType="sharp-duotone-solid">
            Developer identifier: `users.groups.size`

            Size reports the number of groups returned in the list. It records collection occupancy for the response.

            * **Enables:** distinguish an empty group collection from one containing the provider-reported number of groups.
            * **Interpretation:** The provider supplies `size` as an integer item count, not bytes; zero and missing are not interchangeable.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-key-102ca35dc74f" title="Key" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.key`

            Key is the unique user key in Jira Data Center. Primary key for joining users to issues, worklogs, and changelogs. It supplies the declared record identity used when repeated ingestions represent the same source row.

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

          <Accordion id="provider-permission-field-jiradatacenter-users-locale-d720bb3c7e68" title="Locale" icon="globe" iconType="sharp-duotone-solid">
            Developer identifier: `users.locale`

            Locale records user's configured locale (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 data center user record; it does not establish a person's real-time physical location.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-name-64c2c38a4514" title="Name" icon="id-card" iconType="sharp-duotone-solid">
            Developer identifier: `users.name`

            Name identifies username / login name of the user. Login identifier for cross-system identity resolution. It is needed to resolve references that repeat the same provider identifier.

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

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

            Self captures the URL of the user's REST API 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 data center user record.
            * **Interpretation:** The provider supplies `self` as a URL or resource locator on each jira data center user record. Availability still follows the provider's permissions and retention.
          </Accordion>

          <Accordion id="provider-permission-field-jiradatacenter-users-timezone-3464a7f10e63" title="Time Zone" icon="location-crosshairs" iconType="sharp-duotone-solid">
            Developer identifier: `users.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 users using the recorded time zone.
            * **Interpretation:** The provider supplies `timeZone` as location or localization context per jira data center user record; it does not establish a person's real-time physical location.
          </Accordion>
        </AccordionGroup>
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="Troubleshooting">
    | Error                | Meaning             | Solution                             |
    | -------------------- | ------------------- | ------------------------------------ |
    | `401 Unauthorized`   | Invalid credentials | Verify username and token/password   |
    | `403 Forbidden`      | No permission       | Check user has required permissions  |
    | `Connection refused` | Network issue       | Verify server URL and network access |

    #### Common Issues

    #### PATs not available

    Personal Access Tokens require Jira 8.14+. For older versions, use Basic Authentication.

    #### SSL certificate errors

    Self-signed certificates may cause issues. Ensure proper certificate configuration.

    **[Jira Server REST API](https://docs.atlassian.com/software/jira/docs/api/REST/latest/)** — Official API documentation
  </Tab>
</Tabs>