Jira Cloud - Parable

Sync issues, projects, and users from Jira Cloud.

Overview
Setup Guide
Permissions
Troubleshooting

Jira Cloud setup

Parable lists one Jira Cloud Provider under Atlassian. In the connection wizard, use Authentication method to choose Email + API Token or OAuth 2.0 Client Credentials (2LO).Both methods sync the same data streams: projects, users, groups, group members, project Browse projects grants, project role actors, issues, changelogs, and comments.

Data streams

This Provider Plugin defines 9 data streams.

Stream	Description	Sync
`projects`	Jira Cloud projects	full
`users`	Jira Cloud users	full
`groups`	Jira Cloud site groups	full
`group_members`	Members of each Jira Cloud site group	full
`project_browse_grants`	Browse projects grants of each project’s permission scheme	full
`project_role_actors`	Actors of each project role that holds Browse projects	full
`issues`	Jira Cloud issues	incremental
`changelogs`	Issue change history	full
`comments`	Issue comments including author and updateAuthor user objects	full

Jira

What You’ll Need

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

Prerequisites

Global permission: Administer Jira. The project_browse_grants and project_role_actors streams read each project’s permission scheme and project roles, and Jira returns them only to an administrator.
Global permission: Browse users and groups, for the users, groups and group_members streams
Project permission: Browse Projects
User emails visible to “Anyone” in Atlassian profile settings

Setup

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

What You’ll Need

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

Prerequisites

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

Setup

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

Jira

Endpoint	API Token permission	OAuth scope
`/rest/api/3/project/search`	Browse Projects	read:jira-work
`/rest/api/3/search/jql`	Browse Projects	read:jira-work
`/rest/api/3/users/search`	Browse users and groups	read:jira-user
`/rest/api/3/group/bulk`	Browse users and groups	read:jira-user
`/rest/api/3/group/member`	Browse users and groups	manage:jira-configuration
`/rest/api/3/project/{key}/permissionscheme`	Administer Jira	manage:jira-configuration
`/rest/api/3/project/{key}/role/{id}`	Administer Jira	manage:jira-configuration
`/rest/api/3/issue/{id}/changelog`	Browse Projects	read:jira-work

Without Administer Jira, or without the manage:jira-configuration scope, Jira refuses the permission scheme and project role reads. Parable then reads no Browse projects grant, so while your Workspace enforces source permissions only people with All data access read Jira Cloud projects and issues.

Who reads Jira Cloud rows

In Jira Cloud, the permission scheme of a project decides who browses it. Its Browse projects permission names users, groups, project roles, every logged-in user (an application role), or anyone. An issue security level hides an issue from people who are not in the level, and a comment’s visibility limits it to a group or a project role.Parable reads Jira Cloud with an administrator’s credential, so it reads every project the credential can open. While your Workspace turns on Enforce source permissions, and on a table where a Provider Policy rule reads Source permissions (Source permissions), each member reads only these Jira Cloud rows:

Tables	Who reads a row
`projects`	Each user that the project’s Browse projects permission names, each member of a group it names, each user and group member that holds a project role it names in that project, and, when it names an application role, every active Jira user with a person (`atlassian`) account
`issues`	The people who read the issue’s project. An issue with a security level reads only for people with All data access.
`comments`	The people who read the comment’s issue. A comment restricted to a group or a project role reads only for people with All data access.
`changelogs`	The people who read the changelog’s issue
`users`, `groups`, `group_members`	Every active Jira user with a person (`atlassian`) account
`project_browse_grants`, `project_role_actors`	Only people with All data access

Parable matches each member to their Jira user by the email they sign in with. Jira returns a user’s email only when the user’s profile shows it, and managed accounts hide it by default. A member whose Jira email is hidden reads no Jira Cloud row until an administrator confirms the link between the member and the Jira account.
Only a person account (accountType atlassian) is a member. A customer account (Jira Service Management), an app account, and an account whose type Jira leaves out are guests. It keeps the grants that name it and its groups, but an application role grant does not admit it.
A Jira user is active only when Jira reports active as true. When Jira leaves active out, Parable treats the user as inactive.
When Jira deactivates or deletes a user, that member reads no Jira Cloud row after the next sync of users. When a person leaves a group, or stops holding a project role that has Browse projects, the change applies after the next sync of group_members or project_role_actors, with no action from you.
People with All data access read every row. Each such read is recorded in your Workspace’s audit events.

Parable does not reproduce some Jira rules. A Browse projects grant to the reporter, the current assignee, the project lead, or a user or group custom field gives no access, because it depends on each issue. A project that grants Browse projects only that way reads only for people with All data access. Parable does not read the members of an issue security level or of a comment’s group or role, so those issues and comments read only for people with All data access. A team-managed project whose permission scheme names no Browse projects grant reads only for people with All data access. An application role grant admits every active Jira user with a person account, also a person without access to that Jira product. The summary of a linked issue, a parent or a subtask shows on the issue that links it, also when the reader cannot browse the linked issue’s project. The issues stream does not read the comments and worklogs that Jira embeds in an issue, because a restricted comment or worklog would read as its issue. The comments stream reads comments with their visibility. No stream reads worklogs.

Changelogs

Developer identifier: changelogsChangelogs contain issue change history.

Enables: reconstruct the field changes recorded for each parent issue.
Scope: Reads every record from GET /rest/api/3/issue/{id}/changelog on each sync. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

Author

Developer identifier: changelogs.authorAuthor captures the user who made the change. It keeps the provider-reported person or account context attached to the record.

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

Account ID

Developer identifier: changelogs.author.accountIdAccount ID captures the Atlassian account ID of the user. Unique, stable identifier. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies accountId as a record-level identifier. Its values are not guaranteed to be unique.

Account Type

Developer identifier: changelogs.author.accountTypeAccount Type captures the type of account (e.g., atlassian, app, customer). It preserves the provider’s current classification of this record.

Enables: separate changelog records by the exact provider-reported account type value when describing their recorded state.
Interpretation: The provider supplies accountType per changelog author record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Active

Developer identifier: changelogs.author.activeActive indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

Enables: select changelog records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per changelog author record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: changelogs.author.avatarUrlsAvatar URLs records URLs for the user’s avatar images in various sizes. It retains the exact provider location for the referenced resource.

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

16x16

Developer identifier: changelogs.author.avatarUrls.16x1616x16 records URL for the 16x16 pixel avatar. It retains the exact provider location for the referenced resource.

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

24x24

Developer identifier: changelogs.author.avatarUrls.24x2424x24 records URL for the 24x24 pixel avatar. It retains the exact provider location for the referenced resource.

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

32x32

Developer identifier: changelogs.author.avatarUrls.32x3232x32 records URL for the 32x32 pixel avatar. It retains the exact provider location for the referenced resource.

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

48x48

Developer identifier: changelogs.author.avatarUrls.48x4848x48 records URL for the 48x48 pixel avatar. It retains the exact provider location for the referenced resource.

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

Display Name

Developer identifier: changelogs.author.displayNameDisplay Name captures the display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

Developer identifier: changelogs.author.emailAddressEmail Address captures the email address of the user, if visible. It keeps the provider-reported person or account context attached to the record.

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

Self

Developer identifier: changelogs.author.selfSelf records REST API URL for this user resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a changelog author record.
Interpretation: The provider supplies self as a URL or resource locator on each changelog author record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: changelogs.author.timeZoneTime Zone captures the IANA time zone of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

Created

Developer identifier: changelogs.createdCreated records ISO 8601 timestamp when the change was made. It anchors the named event or boundary on the record’s timeline.

Enables: place changelog records on a timeline by created and select the records within an explicit reporting window.
Interpretation: The provider supplies created per jira cloud changelog record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

History Metadata

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

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

Activity Description

Developer identifier: changelogs.historyMetadata.activityDescriptionActivity Description contains a description of the activity that triggered the change. It keeps the exact text, label, or authored value needed to interpret the record.

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

Activity Description Key

Developer identifier: changelogs.historyMetadata.activityDescriptionKeyActivity Description Key captures the key of the activity description. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same activity description key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies activityDescriptionKey as a record-level identifier. Its values are not guaranteed to be unique.

Actor

Developer identifier: changelogs.historyMetadata.actorActor captures the user or system that performed the change. It keeps the provider-reported person or account context attached to the record.

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

Avatar URL

Developer identifier: changelogs.historyMetadata.actor.avatarUrlAvatar URL captures the URL of the participant’s avatar. It retains the exact provider location for the referenced resource.

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

Display Name

Developer identifier: changelogs.historyMetadata.actor.displayNameDisplay Name captures the display name of the participant. It keeps the exact text, label, or authored value needed to interpret the record.

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

Display Name Key

Developer identifier: changelogs.historyMetadata.actor.displayNameKeyDisplay Name Key captures the key of the display name of the participant. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same display name key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies displayNameKey as a record-level identifier. Its values are not guaranteed to be unique.

Developer identifier: changelogs.historyMetadata.actor.idID captures the ID of the participant. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Type

Developer identifier: changelogs.historyMetadata.actor.typeType captures the type of the participant. It preserves the provider’s current classification of this record.

Enables: separate changelog records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per history metadata participant record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

URL

Developer identifier: changelogs.historyMetadata.actor.urlURL captures the URL of the participant. It retains the exact provider location for the referenced resource.

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

Cause

Developer identifier: changelogs.historyMetadata.causeCause captures the cause of the change (e.g., an automation rule or webhook). It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Description

Developer identifier: changelogs.historyMetadata.descriptionDescription contains a description of the history record. It keeps the exact text, label, or authored value needed to interpret the record.

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

Description Key

Developer identifier: changelogs.historyMetadata.descriptionKeyDescription Key captures the description key of the history record. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same description key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies descriptionKey as a record-level identifier. Its values are not guaranteed to be unique.

Email Description

Developer identifier: changelogs.historyMetadata.emailDescriptionEmail Description captures the description of the email address associated with the history record. It keeps the exact text, label, or authored value needed to interpret the record.

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

Email Description Key

Developer identifier: changelogs.historyMetadata.emailDescriptionKeyEmail Description Key captures the description key of the email address. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same email description key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies emailDescriptionKey as a record-level identifier. Its values are not guaranteed to be unique.

Extra Data

Developer identifier: changelogs.historyMetadata.extraDataExtra Data records additional arbitrary metadata associated with the history record. It holds configured attributes whose keys and shapes can vary.

Enables: interpret extra data according to the provider and Workspace configuration that produced each changelog record.
Interpretation: Keys and value shapes within extraData can vary with provider and customer configuration. Check the keys in your Workspace’s data rather than assume a fixed set.

Generator

Developer identifier: changelogs.historyMetadata.generatorGenerator captures the system or integration that generated the change. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Type

Developer identifier: changelogs.historyMetadata.typeType captures the type of the history record. It preserves the provider’s current classification of this record.

Enables: separate changelog records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per history metadata record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Developer identifier: changelogs.idID is the unique ID of the changelog entry. It is the record key. Rows with the same value describe the same record.

Enables: identify each jira cloud changelog record across syncs.
Interpretation: The provider supplies id at one value per jira cloud changelog record, and it is the record key.

Issue ID

Developer identifier: changelogs.issue_idIssue ID identifies the parent issue. Parable copies its ID from the parent record in issues. Absent from the Jira changelog API response body itself. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same issue ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies issue_id as a record-level identifier. Its values are not guaranteed to be unique.

Issue Key

Developer identifier: changelogs.issue_keyIssue Key identifies the key of the parent issue (e.g. PROJ-42). Parable copies it from the parent record in issues. It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same issue key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies issue_key as a record-level identifier. Its values are not guaranteed to be unique.

Items

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

Enables: enumerate the nested items records contained by each jira cloud changelog record.
Interpretation: The provider returns items as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Field

Developer identifier: changelogs.items.fieldField captures the human-readable name of the field that changed (e.g., ‘status’, ‘assignee’, ‘priority’). It keeps the exact text, label, or authored value needed to interpret the record.

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

Field ID

Developer identifier: changelogs.items.fieldIdField ID captures the ID of the field that changed. For system fields this is the field name; for custom fields it is the custom field ID (e.g., ‘customfield_10010’).

Enables: Match changelog item entries on fieldId; it is not a record key, so each entry is identified by its position in the array.
Interpretation: The provider supplies fieldId at one value per changelog item record.

Fieldtype

Developer identifier: changelogs.items.fieldtypeFieldtype captures the type of the field that changed (e.g., ‘jira’, ‘custom’). It holds configured attributes whose keys and shapes can vary.

Enables: interpret fieldtype according to the provider and Workspace configuration that produced each changelog record.
Interpretation: Keys and value shapes within fieldtype can vary with provider and customer configuration. Check the keys in your Workspace’s data rather than assume a fixed set.

From

Developer identifier: changelogs.items.fromFrom captures the ID or machine-readable value of the field before the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

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

From String

Developer identifier: changelogs.items.fromStringFrom String captures the human-readable display value of the field before the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

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

Tmp From Account ID

Developer identifier: changelogs.items.tmpFromAccountIdTmp From Account ID captures the account ID of the user in the ‘from’ value, when the field change involves a user (e.g., assignee changes). It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same tmp from account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies tmpFromAccountId as a record-level identifier. Its values are not guaranteed to be unique.

Tmp To Account ID

Developer identifier: changelogs.items.tmpToAccountIdTmp To Account ID captures the account ID of the user in the ‘to’ value, when the field change involves a user (e.g., assignee changes). It is needed to resolve references that repeat the same provider identifier.

Enables: match changelog records to provider records that carry the same tmp to account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies tmpToAccountId as a record-level identifier. Its values are not guaranteed to be unique.

Developer identifier: changelogs.items.toTo captures the ID or machine-readable value of the field after the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

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

To String

Developer identifier: changelogs.items.toStringTo String captures the human-readable display value of the field after the change. It preserves the recorded before, after, or contextual value needed to explain a change event.

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

Comments

Developer identifier: commentsComments contain issue comments including author and updateAuthor user objects.

Enables: inspect issue-comment content with author, updater, visibility, and timestamp context.
Scope: Reads every record from GET /rest/api/3/issue/{id}/comment on each sync. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent. has_visibility is true when the comment is restricted to a group or a project role.

Author

Developer identifier: comments.authorAuthor records user who authored the comment. It keeps the provider-reported person or account context attached to the record.

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

Account ID

Developer identifier: comments.author.accountIdAccount ID captures the Atlassian account ID of the user. Unique, stable identifier. It is needed to resolve references that repeat the same provider identifier.

Enables: match comment records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies accountId as a record-level identifier. Its values are not guaranteed to be unique.

Account Type

Developer identifier: comments.author.accountTypeAccount Type captures the type of account (e.g., atlassian, app, customer). It preserves the provider’s current classification of this record.

Enables: separate comment records by the exact provider-reported account type value when describing their recorded state.
Interpretation: The provider supplies accountType per comment author record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Active

Developer identifier: comments.author.activeActive indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

Enables: select comment records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per comment author record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: comments.author.avatarUrlsAvatar URLs records URLs for the user’s avatar images in various sizes. It retains the exact provider location for the referenced resource.

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

16x16

Developer identifier: comments.author.avatarUrls.16x1616x16 records URL for the 16x16 pixel avatar. It retains the exact provider location for the referenced resource.

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

24x24

Developer identifier: comments.author.avatarUrls.24x2424x24 records URL for the 24x24 pixel avatar. It retains the exact provider location for the referenced resource.

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

32x32

Developer identifier: comments.author.avatarUrls.32x3232x32 records URL for the 32x32 pixel avatar. It retains the exact provider location for the referenced resource.

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

48x48

Developer identifier: comments.author.avatarUrls.48x4848x48 records URL for the 48x48 pixel avatar. It retains the exact provider location for the referenced resource.

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

Display Name

Developer identifier: comments.author.displayNameDisplay Name captures the display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

Developer identifier: comments.author.emailAddressEmail Address captures the email address of the user, if visible. It keeps the provider-reported person or account context attached to the record.

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

Self

Developer identifier: comments.author.selfSelf records REST API URL for this user resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a comment author record.
Interpretation: The provider supplies self as a URL or resource locator on each comment author record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: comments.author.timeZoneTime Zone captures the IANA time zone of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

Body

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

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

Created

Developer identifier: comments.createdCreated records the timestamp when the comment was created. It anchors the named event or boundary on the record’s timeline.

Enables: place comment records on a timeline by created and select the records within an explicit reporting window.
Interpretation: The provider supplies created per jira cloud comment record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Has Visibility

Developer identifier: comments.has_visibilityHas Visibility indicates whether the comment is restricted to a group or a project role. Parable computes it from visibility when it reads the comment, and always writes true or false.

Enables: select restricted comments. For source permissions, a restricted comment does not inherit its issue’s readers, so only people with All data access read it.
Interpretation: Jira shows a restricted comment only to the group or role that visibility names. Parable does not resolve that group or role for the comment.

Developer identifier: comments.idID is the unique identifier for the comment. It is the record key. Rows with the same value describe the same record.

Enables: identify each jira cloud comment record across syncs.
Interpretation: The provider supplies id at one value per jira cloud comment record, and it is the record key.

Issue ID

Developer identifier: comments.issue_idIssue ID identifies the parent issue. Parable copies its ID from the parent record in issues. Absent from the Jira comments API response body itself. It is needed to resolve references that repeat the same provider identifier.

Enables: match comment records to provider records that carry the same issue ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies issue_id as a record-level identifier. Its values are not guaranteed to be unique.

Issue Key

Developer identifier: comments.issue_keyIssue Key identifies the key of the parent issue (e.g. PROJ-42). Parable copies it from the parent record in issues. It is needed to resolve references that repeat the same provider identifier.

Enables: match comment records to provider records that carry the same issue key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies issue_key as a record-level identifier. Its values are not guaranteed to be unique.

Jsd Public

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

Enables: select comment records for which the provider reports jsd public as true or false.
Interpretation: The provider supplies jsdPublic as a boolean per jira cloud comment record; false and missing are distinct when the field is optional. In Jira Cloud, jsd public is a condition on the work record, not a measure of a person’s performance.

Self

Developer identifier: comments.selfSelf records REST API URL for this comment. It retains the exact provider location for the referenced resource.

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

Update Author

Developer identifier: comments.updateAuthorUpdate Author records user who last updated the comment. It keeps the provider-reported person or account context attached to the record.

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

Updated

Developer identifier: comments.updatedUpdated records the timestamp when the comment was last updated. It anchors the named event or boundary on the record’s timeline.

Enables: place comment records on a timeline by updated and select the records within an explicit reporting window.
Interpretation: The provider supplies updated per jira cloud comment record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Visibility

Developer identifier: comments.visibilityVisibility states visibility restriction for the comment. It documents the access-related value reported for this object or membership.

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

Identifier

Developer identifier: comments.visibility.identifierIdentifier is the identifier of the group or role. It is needed to resolve references that repeat the same provider identifier.

Enables: match comment records to provider records that carry the same identifier, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies identifier as a record-level identifier. Its values are not guaranteed to be unique.

Type

Developer identifier: comments.visibility.typeType states type of visibility restriction (group or role). It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported type attached to each visibility object record.
Interpretation: The provider supplies type at visibility object granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, type describes access or membership, not a person’s performance.

Value

Developer identifier: comments.visibility.valueValue 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.

Group Members

Developer identifier: group_membersGroup Members contain the user accounts that belong to each Jira Cloud site group.

Enables: resolve which users hold a group’s Browse projects grants and project roles, so source permissions give each member the group’s tokens.
Scope: Reads every record from GET /rest/api/3/group/member for each group in groups on each sync, inactive users included. A later complete read treats a previously seen membership that is absent as removed, so a person removed from a group loses its access after the next sync. One row per group and account: the key is a digest of group_id and accountId.

Account ID

Developer identifier: group_members.accountIdAccount ID identifies the member’s Atlassian account. It is needed to resolve references that repeat the same provider identifier.

Enables: match each membership to the users record with the same account ID.
Interpretation: The provider supplies accountId once per member of the group. For source permissions, Parable marks this field as the user who holds the membership.

Account Type

Developer identifier: group_members.accountTypeAccount Type states the type of the member’s account. It preserves the provider’s classification of the account.

Enables: separate person accounts from app and customer accounts in a group.
Interpretation: The provider supplies accountType per member using its own vocabulary. The users record of the account decides whether it is a guest.

Active

Developer identifier: group_members.activeActive indicates whether the member’s account is active. It preserves the provider-reported yes-or-no condition.

Enables: see inactive members of a group.
Interpretation: The provider supplies active per member. The users record of the account decides whether the account gives tokens.

Display Name

Developer identifier: group_members.displayNameDisplay Name records the member’s display name. It keeps the provider-reported account context attached to the membership.

Enables: show who a membership names.
Interpretation: The provider supplies displayName per member. A name labels an account but never joins two.

Group ID

Developer identifier: group_members.group_idGroup ID identifies the group of the membership. Parable copies it from the parent record in groups. Jira Cloud does not return this value with the record.

Enables: match each membership to its group.
Interpretation: For source permissions, Parable marks this field as the group the member belongs to.

Membership Key

Developer identifier: group_members.membership_keyMembership Key identifies one membership of one account in one group. Parable computes it from group_id and accountId.

Enables: keep one row per group and member across syncs.
Interpretation: The value is a digest, not a Jira identifier.

Groups

Developer identifier: groupsGroups contain the Jira Cloud site groups.

Enables: resolve the groups that project permission schemes and project roles name, and supply the group principals that source permissions match Browse projects grants against.
Scope: Reads every record from GET /rest/api/3/group/bulk on each sync. The credential needs the Browse users and groups global permission. A later complete read treats a previously seen group that is absent as removed.

Group ID

Developer identifier: groups.groupIdGroup ID is the stable identifier of the group. It is the record key, so rows with the same value describe the same record.

Enables: identify each Jira Cloud group across syncs, and match it to group_members.group_id, to group holders in project_browse_grants and to group actors in project_role_actors.
Interpretation: The provider supplies groupId at one value per group, and it is the record key. For source permissions, Parable marks this field as the ID of a group principal.

Name

Developer identifier: groups.nameName records the display name of the group. It keeps the exact label needed to interpret the record.

Enables: show which Jira Cloud group a membership or a grant names.
Interpretation: The provider supplies name per group. An administrator can rename a group, so the name is not a stable identifier.

Issues

Developer identifier: issuesIssues contain Jira Cloud issues via enhanced JQL search.

Enables: report issue content, state, priority, assignment, and project context without treating work state as individual performance.
Scope: Reads the records that changed since the previous sync from POST /rest/api/3/search/jql. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent. The request leaves out the embedded comment and worklog fields, because a restricted comment or worklog would otherwise read as its issue. The comments tap reads comments with their visibility. No tap reads worklogs. has_security_level is true when the issue has a security level.

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

Changelog

Developer identifier: issues.changelogChangelog records changelog of field changes, present when expand=changelog is requested. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Histories

Developer identifier: issues.changelog.historiesHistories records list of changelog history entries. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: enumerate the nested histories records contained by each changelog container record.
Interpretation: The provider returns histories as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Author

Developer identifier: issues.changelog.histories.authorAuthor records user who made the changes. It keeps the provider-reported person or account context attached to the record.

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

Account ID

Developer identifier: issues.changelog.histories.author.accountIdAccount ID is the unique Atlassian account ID for the user. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies accountId as a record-level identifier. Its values are not guaranteed to be unique.

Account Type

Developer identifier: issues.changelog.histories.author.accountTypeAccount Type states type of account (atlassian, app, customer). It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported account type value when describing their recorded state.
Interpretation: The provider supplies accountType per user object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Active

Developer identifier: issues.changelog.histories.author.activeActive indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per user object record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: issues.changelog.histories.author.avatarUrlsAvatar URLs records avatar image URLs at various sizes. It retains the exact provider location for the referenced resource.

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

16x16

Developer identifier: issues.changelog.histories.author.avatarUrls.16x1616x16 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.

24x24

Developer identifier: issues.changelog.histories.author.avatarUrls.24x2424x24 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.

32x32

Developer identifier: issues.changelog.histories.author.avatarUrls.32x3232x32 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.

48x48

Developer identifier: issues.changelog.histories.author.avatarUrls.48x4848x48 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.

Display Name

Developer identifier: issues.changelog.histories.author.displayNameDisplay Name records display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

Developer identifier: issues.changelog.histories.author.emailAddressEmail Address records email address of the user (if visible). It keeps the provider-reported person or account context attached to the record.

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

Self

Developer identifier: issues.changelog.histories.author.selfSelf records REST API URL for this user. It retains the exact provider location for the referenced resource.

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

Time Zone

Developer identifier: issues.changelog.histories.author.timeZoneTime Zone records user’s configured timezone. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

Created

Developer identifier: issues.changelog.histories.createdCreated records the timestamp when the changes were made. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by created and select the records within an explicit reporting window.
Interpretation: The provider supplies created per changelog history record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Developer identifier: issues.changelog.histories.idID is the unique identifier for this changelog entry. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Items

Developer identifier: issues.changelog.histories.itemsItems records individual field changes in this changelog entry. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: enumerate the nested items records contained by each changelog history record.
Interpretation: The provider returns items as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Field

Developer identifier: issues.changelog.histories.items.fieldField records name of the field that changed. It keeps the exact text, label, or authored value needed to interpret the record.

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

Field ID

Developer identifier: issues.changelog.histories.items.fieldIdField ID is the ID of the field that changed. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same field ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies fieldId as a record-level identifier. Its values are not guaranteed to be unique.

Fieldtype

Developer identifier: issues.changelog.histories.items.fieldtypeFieldtype records type of the field (jira, custom). It holds configured attributes whose keys and shapes can vary.

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. Check the keys in your Workspace’s data rather than assume a fixed set.

From

Developer identifier: issues.changelog.histories.items.fromFrom records previous value ID or key. It preserves the recorded before, after, or contextual value needed to explain a change event.

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

From String

Developer identifier: issues.changelog.histories.items.fromStringFrom 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.

Developer identifier: issues.changelog.histories.items.toTo records new value ID or key. It preserves the recorded before, after, or contextual value needed to explain a change event.

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

To String

Developer identifier: issues.changelog.histories.items.toStringTo 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.

Max Results

Developer identifier: issues.changelog.maxResultsMax Results reports maximum number of history entries returned. It preserves the stated measure at this record’s granularity.

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

Start At

Developer identifier: issues.changelog.startAtStart At is the position of the first changelog entry in the list that Jira returned with the issue. It locates that page within the issue’s complete history.

Enables: detect partial changelog pages and continue interpretation with maxResults and total.
Interpretation: The provider supplies startAt as a zero-based position, not a history count or business measure; zero denotes the first entry.

Total

Developer identifier: issues.changelog.totalTotal reports the total number of history entries. It preserves the stated measure at this record’s granularity.

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

Expand

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

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

Fields

Developer identifier: issues.fieldsFields records all fields of the issue. It holds configured attributes whose keys and shapes can vary.

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. Check the keys in your Workspace’s data rather than assume a fixed set.

Aggregateprogress

Developer identifier: issues.fields.aggregateprogressAggregateprogress groups time spent, total estimated time, and completion percentage for the issue and its subtasks. It keeps the rollup separate from issue-only progress.

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

Percent

Developer identifier: issues.fields.aggregateprogress.percentPercent reports issue completion on a 0–100 percentage scale. It summarizes the relationship between time spent and the total estimate.

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

Progress

Developer identifier: issues.fields.aggregateprogress.progressProgress reports time spent in seconds. It preserves the elapsed interval reported for this record.

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

Total

Developer identifier: issues.fields.aggregateprogress.totalTotal reports the total estimated time in seconds. It preserves the elapsed interval reported for this record.

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

Aggregatetimeestimate

Developer identifier: issues.fields.aggregatetimeestimateAggregatetimeestimate 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.

Aggregatetimeoriginalestimate

Developer identifier: issues.fields.aggregatetimeoriginalestimateAggregatetimeoriginalestimate 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.

Aggregatetimespent

Developer identifier: issues.fields.aggregatetimespentAggregatetimespent 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.

Assignee

Developer identifier: issues.fields.assigneeAssignee records user assigned to this issue. It keeps the provider-reported person or account context attached to the record.

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

Attachment

Developer identifier: issues.fields.attachmentAttachment records file attachments on this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: enumerate the nested attachment records contained by each issue field record.
Interpretation: The provider returns attachment as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Author

Developer identifier: issues.fields.attachment.authorAuthor records user who uploaded the attachment. It keeps the provider-reported person or account context attached to the record.

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

Content

Developer identifier: issues.fields.attachment.contentContent records URL to download the attachment content. It keeps the exact text, label, or authored value needed to interpret the record.

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

Created

Developer identifier: issues.fields.attachment.createdCreated records the timestamp when the attachment was uploaded. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by created and select the records within an explicit reporting window.
Interpretation: The provider supplies created per attachment object record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Filename

Developer identifier: issues.fields.attachment.filenameFilename records name of the attached file. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.attachment.idID is the unique identifier for the attachment. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

MIME Type

Developer identifier: issues.fields.attachment.mimeTypeMIME Type states MIME type of the attachment. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported MIME type value when describing their recorded state.
Interpretation: The provider supplies mimeType per attachment object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.attachment.selfSelf records REST API URL for this attachment. It retains the exact provider location for the referenced resource.

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

Size

Developer identifier: issues.fields.attachment.sizeSize 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.

Thumbnail

Developer identifier: issues.fields.attachment.thumbnailThumbnail records URL for the attachment thumbnail. It retains the exact provider location for the referenced resource.

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

Closed Sprints

Developer identifier: issues.fields.closedSprintsClosed Sprints records closed sprints this issue was part of. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by closed sprints and select the records within an explicit reporting window.
Interpretation: The provider supplies closedSprints per issue field record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Board ID

Developer identifier: issues.fields.closedSprints.boardIdBoard ID is the ID of the board this sprint belongs to. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same board ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies boardId as a record-level identifier. Its values are not guaranteed to be unique.

Completion Date

Developer identifier: issues.fields.closedSprints.completeDateCompletion Date records the date the sprint was completed. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by completion date and select the records within an explicit reporting window.
Interpretation: The provider supplies completeDate per sprint object record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

End Date

Developer identifier: issues.fields.closedSprints.endDateEnd Date records end date of the sprint. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by end date and select the records within an explicit reporting window.
Interpretation: The provider supplies endDate per sprint object record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Goal

Developer identifier: issues.fields.closedSprints.goalGoal records goal of the sprint. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.closedSprints.idID is the unique identifier for the sprint. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.closedSprints.nameName records name of the sprint. It keeps the exact text, label, or authored value needed to interpret the record.

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

Self

Developer identifier: issues.fields.closedSprints.selfSelf records REST API URL for this sprint. It retains the exact provider location for the referenced resource.

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

Start Date

Developer identifier: issues.fields.closedSprints.startDateStart Date records start date of the sprint. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by start date and select the records within an explicit reporting window.
Interpretation: The provider supplies startDate per sprint object record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

State

Developer identifier: issues.fields.closedSprints.stateState states current state of the sprint. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported state value when describing their recorded state.
Interpretation: The provider supplies state per sprint object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Components

Developer identifier: issues.fields.componentsComponents records components associated with this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Description

Developer identifier: issues.fields.components.descriptionDescription records description of the component. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.components.idID is the unique identifier for the component. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.components.nameName records name of the component. It keeps the exact text, label, or authored value needed to interpret the record.

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

Self

Developer identifier: issues.fields.components.selfSelf records REST API URL for this component. It retains the exact provider location for the referenced resource.

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

Created

Developer identifier: issues.fields.createdCreated 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.

Creator

Developer identifier: issues.fields.creatorCreator records user who created this issue. It keeps the provider-reported person or account context attached to the record.

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

Description

Developer identifier: issues.fields.descriptionDescription records issue description in Atlassian Document Format (ADF). It keeps the exact text, label, or authored value needed to interpret the record.

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

Duedate

Developer identifier: issues.fields.duedateDuedate 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.

Environment

Developer identifier: issues.fields.environmentEnvironment states environment field in ADF format. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported environment value when describing their recorded state.
Interpretation: The provider supplies environment per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Epic

Developer identifier: issues.fields.epicEpic records epic this issue belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Fields

Developer identifier: issues.fields.epic.fieldsFields records summary fields of the referenced issue. It holds configured attributes whose keys and shapes can vary.

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. Check the keys in your Workspace’s data rather than assume a fixed set.

Issuetype

Developer identifier: issues.fields.epic.fields.issuetypeIssuetype states issue type of the referenced issue. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported issuetype value when describing their recorded state.
Interpretation: The provider supplies issuetype per issue reference summary field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.epic.fields.issuetype.descriptionDescription records description of the issue type. It keeps the exact text, label, or authored value needed to interpret the record.

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

Hierarchy Level

Developer identifier: issues.fields.epic.fields.issuetype.hierarchyLevelHierarchy Level states hierarchy level of this issue type.

Enables: filter and group issue records by the Jira Cloud issue type hierarchy level exposed by the nested object.
Interpretation: The provider supplies hierarchyLevel per issue type object record as a number; unknown and missing values must remain distinct.

Icon URL

Developer identifier: issues.fields.epic.fields.issuetype.iconUrlIcon URL records URL of the issue type icon. It retains the exact provider location for the referenced resource.

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

Developer identifier: issues.fields.epic.fields.issuetype.idID is the unique identifier for the issue type. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.epic.fields.issuetype.nameName states name of the issue type. It preserves the provider’s current classification of this record.

Enables: filter and group issue records by the Jira Cloud issue type name exposed by the nested object.
Interpretation: The provider supplies name per issue type object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.epic.fields.issuetype.selfSelf records REST API URL for this issue type. It retains the exact provider location for the referenced resource.

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

Subtask

Developer identifier: issues.fields.epic.fields.issuetype.subtaskSubtask indicates whether this issue type represents subtasks. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports subtask as true or false.
Interpretation: The provider supplies subtask as a boolean per issue type object record; false and missing are distinct when the field is optional. In Jira Cloud, subtask is a condition on the work record, not a measure of a person’s performance.

Priority

Developer identifier: issues.fields.epic.fields.priorityPriority states priority of the referenced issue. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per issue reference summary field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.epic.fields.priority.descriptionDescription records description of the priority. It keeps the exact text, label, or authored value needed to interpret the record.

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

Icon URL

Developer identifier: issues.fields.epic.fields.priority.iconUrlIcon URL records URL of the priority icon. It retains the exact provider location for the referenced resource.

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

Developer identifier: issues.fields.epic.fields.priority.idID is the unique identifier for the priority. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.epic.fields.priority.nameName states name of the priority level. It preserves the provider’s current classification of this record.

Enables: filter and group issue records by the Jira Cloud priority name exposed by the nested object.
Interpretation: The provider supplies name per priority object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.epic.fields.priority.selfSelf records REST API URL for this priority. It retains the exact provider location for the referenced resource.

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

Status

Developer identifier: issues.fields.epic.fields.statusStatus states status of the referenced issue. It preserves the provider’s current classification of this record.

Enables: filter issue records to a selected Jira status and group issue counts by that exact workflow classification.
Interpretation: The provider supplies status per issue reference summary field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.epic.fields.status.descriptionDescription records description of the status. It keeps the exact text, label, or authored value needed to interpret the record.

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

Icon URL

Developer identifier: issues.fields.epic.fields.status.iconUrlIcon URL records URL of the status icon. It retains the exact provider location for the referenced resource.

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

Developer identifier: issues.fields.epic.fields.status.idID is the unique identifier for the status. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.epic.fields.status.nameName states display name of the status. It preserves the provider’s current classification of this record.

Enables: filter and group issue records by the Jira Cloud status name exposed by the nested object.
Interpretation: The provider supplies name per status object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.epic.fields.status.selfSelf records REST API URL for this status. It retains the exact provider location for the referenced resource.

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

Status Category

Developer identifier: issues.fields.epic.fields.status.statusCategoryStatus Category states category grouping for this status. It preserves the provider’s current classification of this record.

Enables: filter issue records to a selected Jira status category and group issue counts by that exact workflow classification.
Interpretation: The provider supplies statusCategory per status object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Color Name

Developer identifier: issues.fields.epic.fields.status.statusCategory.colorNameColor Name records color associated with this category. It preserves the provider’s visual treatment for the represented object.

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

Developer identifier: issues.fields.epic.fields.status.statusCategory.idID is the unique identifier for the status category. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Key

Developer identifier: issues.fields.epic.fields.status.statusCategory.keyKey is the key of the status category. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies key as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.epic.fields.status.statusCategory.nameName states display name of the status category. It preserves the provider’s current classification of this record.

Enables: filter and group issue records by the Jira Cloud status category name exposed by the nested object.
Interpretation: The provider supplies name per status category object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.epic.fields.status.statusCategory.selfSelf records REST API URL for this status category. It retains the exact provider location for the referenced resource.

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

Summary

Developer identifier: issues.fields.epic.fields.summarySummary 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.

Developer identifier: issues.fields.epic.idID is the unique identifier of the referenced issue. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Key

Developer identifier: issues.fields.epic.keyKey identifies human-readable key of the referenced issue. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies key as a record-level identifier. Its values are not guaranteed to be unique.

Self

Developer identifier: issues.fields.epic.selfSelf 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.

Fix Versions

Developer identifier: issues.fields.fixVersionsFix Versions records fix versions associated with this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Archived

Developer identifier: issues.fields.fixVersions.archivedArchived indicates whether this version is archived. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports archived as true or false.
Interpretation: The provider supplies archived as a boolean per version object record; false and missing are distinct when the field is optional. In Jira Cloud, archived is a condition on the work record, not a measure of a person’s performance.

Description

Developer identifier: issues.fields.fixVersions.descriptionDescription records description of the version. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.fixVersions.idID is the unique identifier for the version. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.fixVersions.nameName records name of the version. It keeps the exact text, label, or authored value needed to interpret the record.

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

Released

Developer identifier: issues.fields.fixVersions.releasedReleased indicates whether this version has been released. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports released as true or false.
Interpretation: The provider supplies released as a boolean per version object record; false and missing are distinct when the field is optional. In Jira Cloud, released is a condition on the work record, not a measure of a person’s performance.

Release Date

Developer identifier: issues.fields.fixVersions.releaseDateRelease Date records release date of the version. It anchors the named event or boundary on the record’s timeline.

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

Self

Developer identifier: issues.fields.fixVersions.selfSelf records REST API URL for this version. It retains the exact provider location for the referenced resource.

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

Issuelinks

Developer identifier: issues.fields.issuelinksIssuelinks 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; an absent value does not prove that no related object exists outside the credential’s visibility.

Developer identifier: issues.fields.issuelinks.idID is the unique identifier for the issue link. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Inward Issue

Developer identifier: issues.fields.issuelinks.inwardIssueInward Issue captures the inward issue in the link relationship. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Outward Issue

Developer identifier: issues.fields.issuelinks.outwardIssueOutward Issue captures the outward issue in the link relationship. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Self

Developer identifier: issues.fields.issuelinks.selfSelf records REST API URL for this link. It retains the exact provider location for the referenced resource.

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

Type

Developer identifier: issues.fields.issuelinks.typeType states type of the link relationship. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per issue link object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Developer identifier: issues.fields.issuelinks.type.idID is the unique identifier for the link type. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Inward

Developer identifier: issues.fields.issuelinks.type.inwardInward records inward description (e.g., ‘is blocked by’). It keeps the exact text, label, or authored value needed to interpret the record.

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

Name

Developer identifier: issues.fields.issuelinks.type.nameName records name of the link type. It keeps the exact text, label, or authored value needed to interpret the record.

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

Outward

Developer identifier: issues.fields.issuelinks.type.outwardOutward records outward description (e.g., ‘blocks’). It keeps the exact text, label, or authored value needed to interpret the record.

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

Self

Developer identifier: issues.fields.issuelinks.type.selfSelf records REST API URL for this link type. It retains the exact provider location for the referenced resource.

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

Issuetype

Developer identifier: issues.fields.issuetypeIssuetype states type of issue (Bug, Story, Task, etc.). It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported issuetype value when describing their recorded state.
Interpretation: The provider supplies issuetype per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Labels

Developer identifier: issues.fields.labelsLabels 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; an absent value does not prove that no related object exists outside the credential’s visibility.

Last Viewed

Developer identifier: issues.fields.lastViewedLast 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.

Parent

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

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

Priority

Developer identifier: issues.fields.priorityPriority states priority level of the issue. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Progress

Developer identifier: issues.fields.progressProgress groups time spent, total estimated time, and completion percentage for the issue itself. It preserves the time-tracking state without including subtask rollups.

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

Project

Developer identifier: issues.fields.projectProject records project this issue belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Avatar URLs

Developer identifier: issues.fields.project.avatarUrlsAvatar URLs records project avatar URLs. It retains the exact provider location for the referenced resource.

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

Developer identifier: issues.fields.project.idID is the unique identifier for the project. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Key

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

Enables: match issue records to provider records that carry the same key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies key as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.project.nameName records display name of the project. It keeps the exact text, label, or authored value needed to interpret the record.

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

Project Category

Developer identifier: issues.fields.project.projectCategoryProject Category states category of the project. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported project category value when describing their recorded state.
Interpretation: The provider supplies projectCategory per project object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.project.projectCategory.descriptionDescription records description of the project category. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.project.projectCategory.idID is the unique identifier for the project category. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.project.projectCategory.nameName states name of the project category. It preserves the provider’s current classification of this record.

Enables: filter and group issue records by the Jira Cloud project category name exposed by the nested object.
Interpretation: The provider supplies name per project category object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.project.projectCategory.selfSelf records REST API URL for this category. It retains the exact provider location for the referenced resource.

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

Project Type Key

Developer identifier: issues.fields.project.projectTypeKeyProject Type Key identifies type of project (software, business, service_desk). It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same project type key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies projectTypeKey as a record-level identifier. Its values are not guaranteed to be unique.

Self

Developer identifier: issues.fields.project.selfSelf records REST API URL for this project. It retains the exact provider location for the referenced resource.

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

Simplified

Developer identifier: issues.fields.project.simplifiedSimplified indicates whether this is a next-gen (simplified) project. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports simplified as true or false.
Interpretation: The provider supplies simplified as a boolean per project object record; false and missing are distinct when the field is optional. In Jira Cloud, simplified is a condition on the work record, not a measure of a person’s performance.

Reporter

Developer identifier: issues.fields.reporterReporter records user who reported this issue. It keeps the provider-reported person or account context attached to the record.

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

Resolution

Developer identifier: issues.fields.resolutionResolution states resolution of the issue if resolved. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported resolution value when describing their recorded state.
Interpretation: The provider supplies resolution per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.resolution.descriptionDescription records description of the resolution. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.resolution.idID is the unique identifier for the resolution. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.resolution.nameName states name of the resolution (e.g., Done, Won’t Do). It preserves the provider’s current classification of this record.

Enables: filter and group issue records by the Jira Cloud resolution name exposed by the nested object.
Interpretation: The provider supplies name per resolution object record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.resolution.selfSelf records REST API URL for this resolution. It retains the exact provider location for the referenced resource.

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

Resolutiondate

Developer identifier: issues.fields.resolutiondateResolutiondate 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.

Security

Developer identifier: issues.fields.securitySecurity states security level of this issue. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported security value when describing their recorded state.
Interpretation: The provider supplies security per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.security.descriptionDescription records description of the security level. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: issues.fields.security.idID is the unique identifier for the security level. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: issues.fields.security.nameName records name of the security level. It keeps the exact text, label, or authored value needed to interpret the record.

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

Self

Developer identifier: issues.fields.security.selfSelf records REST API URL for this security level. It retains the exact provider location for the referenced resource.

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

Sprint

Developer identifier: issues.fields.sprintSprint states active sprint this issue is in (from Jira Software). It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported sprint value when describing their recorded state.
Interpretation: The provider supplies sprint per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Status

Developer identifier: issues.fields.statusStatus states current workflow status of the issue. It preserves the provider’s current classification of this record.

Enables: filter issue records to a selected Jira status and group issue counts by that exact workflow classification.
Interpretation: The provider supplies status per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Statuscategorychangedate

Developer identifier: issues.fields.statuscategorychangedateStatuscategorychangedate records the timestamp when the status category last changed. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by statuscategorychangedate and select the records within an explicit reporting window.
Interpretation: The provider supplies statuscategorychangedate per issue field record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Story Points

Developer identifier: issues.fields.storyPointsStory Points records story points estimate (custom field, commonly mapped). It holds configured attributes whose keys and shapes can vary.

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. Check the keys in your Workspace’s data rather than assume a fixed set.

Subtasks

Developer identifier: issues.fields.subtasksSubtasks 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; an absent value does not prove that no related object exists outside the credential’s visibility.

Summary

Developer identifier: issues.fields.summarySummary records short title describing the issue. It keeps the exact text, label, or authored value needed to interpret the record.

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

Timeestimate

Developer identifier: issues.fields.timeestimateTimeestimate 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.

Timeoriginalestimate

Developer identifier: issues.fields.timeoriginalestimateTimeoriginalestimate 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.

Timespent

Developer identifier: issues.fields.timespentTimespent 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.

Timetracking

Developer identifier: issues.fields.timetrackingTimetracking 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; an absent value does not prove that no related object exists outside the credential’s visibility.

Original Estimate

Developer identifier: issues.fields.timetracking.originalEstimateOriginal Estimate records the issue’s original planned duration in Jira’s human-readable format. It preserves the planning interval alongside its seconds representation.

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

Original Estimate Seconds

Developer identifier: issues.fields.timetracking.originalEstimateSecondsOriginal Estimate Seconds reports original estimate in seconds. It preserves the elapsed interval reported for this record.

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

Remaining Estimate

Developer identifier: issues.fields.timetracking.remainingEstimateRemaining 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.

Remaining Estimate Seconds

Developer identifier: issues.fields.timetracking.remainingEstimateSecondsRemaining Estimate Seconds reports remaining estimate in seconds. It preserves the elapsed interval reported for this record.

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

Time Spent

Developer identifier: issues.fields.timetracking.timeSpentTime Spent reports human-readable total time spent. It preserves the elapsed interval reported for this record.

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

Time Spent Seconds

Developer identifier: issues.fields.timetracking.timeSpentSecondsTime Spent Seconds reports the total time spent in seconds. It preserves the elapsed interval reported for this record.

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

Updated

Developer identifier: issues.fields.updatedUpdated records the timestamp when the issue was last updated. It anchors the named event or boundary on the record’s timeline.

Enables: place issue records on a timeline by updated and select the records within an explicit reporting window.
Interpretation: The provider supplies updated per issue field record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Versions

Developer identifier: issues.fields.versionsVersions records affects versions associated with this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Votes

Developer identifier: issues.fields.votesVotes records vote information for this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Has Voted

Developer identifier: issues.fields.votes.hasVotedHas Voted indicates whether the current user has voted. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports has voted as true or false.
Interpretation: The provider supplies hasVoted as a boolean per votes object record; false and missing are distinct when the field is optional. In Jira Cloud, has voted is a condition on the work record, not a measure of a person’s performance.

Self

Developer identifier: issues.fields.votes.selfSelf records REST API URL for votes. It retains the exact provider location for the referenced resource.

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

Votes

Developer identifier: issues.fields.votes.votesVotes reports the number of votes. It preserves the stated measure at this record’s granularity.

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

Watches

Developer identifier: issues.fields.watchesWatches records watch information for this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Is Watching

Developer identifier: issues.fields.watches.isWatchingIs Watching indicates whether the current user is watching. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports is watching as true or false.
Interpretation: The provider supplies isWatching as a boolean per watches object record; false and missing are distinct when the field is optional. In Jira Cloud, is watching is a condition on the work record, not a measure of a person’s performance.

Self

Developer identifier: issues.fields.watches.selfSelf records REST API URL for watches. It retains the exact provider location for the referenced resource.

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

Watch Count

Developer identifier: issues.fields.watches.watchCountWatch Count reports the number of watchers. It preserves the stated measure at this record’s granularity.

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

Workratio

Developer identifier: issues.fields.workratioWorkratio reports the issue’s work ratio as a percentage. It relates recorded work to the available estimate.

Enables: identify issues consuming more or less effort than planned and separate issues that lack an estimate.
Interpretation: The provider supplies workratio as an integer percentage and uses -1 when no estimate applies; -1, zero, and missing have different meanings.

Has Security Level

Developer identifier: issues.has_security_levelHas Security Level indicates whether the issue has an issue security level. Parable computes it from fields.security when it reads the issue, and always writes true or false.

Enables: select secured issues. For source permissions, a secured issue does not inherit its project’s readers, so only people with All data access read it.
Interpretation: Jira hides a secured issue from users who are not in the level. Parable does not read level members.

Developer identifier: issues.idID is the unique numeric identifier for the issue. It is the record key, so rows with the same value describe the same record.

Enables: identify each jira cloud issue record across syncs.
Interpretation: The provider supplies id at one value per jira cloud issue record, and it is the record key.

Key

Developer identifier: issues.keyKey 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. Its values are not guaranteed to be unique.

Names

Developer identifier: issues.namesNames records map of field IDs to human-readable field names, present when expand=names is requested. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact names when validating the configuration or technical definition of a jira cloud issue record.
Interpretation: The provider supplies names as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Operations

Developer identifier: issues.operationsOperations records available operations on this issue. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact operations when validating the configuration or technical definition of a jira cloud issue record.
Interpretation: The provider supplies operations as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Project Key

Developer identifier: issues.project_keyProject Key identifies the key of the parent record in projects, and Parable copies it from that record. Jira Cloud does not return this value with the record. 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. Its values are not guaranteed to be unique.

Rendered Fields

Developer identifier: issues.renderedFieldsRendered Fields records HTML-rendered versions of fields, present when expand=renderedFields is requested. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact rendered fields when validating the configuration or technical definition of a jira cloud issue record.
Interpretation: The provider supplies renderedFields as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Self

Developer identifier: issues.selfSelf records REST API URL for this issue. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a jira cloud issue record.
Interpretation: The provider supplies self as a URL or resource locator on each jira cloud issue record. Availability still follows the provider’s permissions and retention.

Transitions

Developer identifier: issues.transitionsTransitions records available workflow transitions for this issue. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: expand the nested transitions object into its declared child fields for each jira cloud issue record.
Interpretation: The provider returns transitions as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Has Screen

Developer identifier: issues.transitions.hasScreenHas Screen indicates whether the transition has an associated screen. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports has screen as true or false.
Interpretation: The provider supplies hasScreen as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, has screen is a condition on the work record, not a measure of a person’s performance.

Developer identifier: issues.transitions.idID is the unique identifier for the transition. It is the key of this nested record.

Enables: identify each issue transition record.
Interpretation: The provider supplies id at one value per issue transition record, and it is the key of this nested record.

Is Conditional

Developer identifier: issues.transitions.isConditionalIs Conditional indicates whether this transition has conditions. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports is conditional as true or false.
Interpretation: The provider supplies isConditional as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, is conditional is a condition on the work record, not a measure of a person’s performance.

Is Global

Developer identifier: issues.transitions.isGlobalIs Global indicates whether this is a global transition. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports is global as true or false.
Interpretation: The provider supplies isGlobal as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, is global is a condition on the work record, not a measure of a person’s performance.

Is Initial

Developer identifier: issues.transitions.isInitialIs Initial indicates whether this is the initial transition. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports is initial as true or false.
Interpretation: The provider supplies isInitial as a boolean per issue transition record; false and missing are distinct when the field is optional. In Jira Cloud, is initial is a condition on the work record, not a measure of a person’s performance.

Name

Developer identifier: issues.transitions.nameName records name of the transition. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each issue transition record.
Interpretation: The provider supplies name at issue transition granularity in the format stated by its description; omitted or redacted content remains unknown.

Developer identifier: issues.transitions.toTo states target status of the transition. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported to value when describing their recorded state.
Interpretation: The provider supplies to per issue transition record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Project Browse Grants

Developer identifier: project_browse_grantsProject Browse Grants contain the Browse projects grants of the permission scheme that each Jira Cloud project uses.

Enables: give each project the users, groups and audiences that may browse it, so source permissions open a project’s issues, comments and changelogs to the same people Jira does. A grant to a project role is expanded into its actors by project_role_actors.
Scope: Reads GET /rest/api/3/project/{key}/permissionscheme?expand=permissions for each project in projects on each sync and keeps only the BROWSE_PROJECTS grants. The credential needs the Administer Jira global permission, or Administer projects on each project. One row per project, holder type and holder value: the key is a digest of project_key, holder_type and holder_value. A later complete read treats a grant that is absent as removed. Only people with All data access read this table.

Grant ID

Developer identifier: project_browse_grants.grant_idGrant ID identifies the permission grant in its permission scheme. Parable lifts it from the grant’s id.

Enables: trace a row to the grant in the Jira permission scheme.
Interpretation: One scheme can serve several projects, so the same grant ID can appear on the rows of several projects.

Grant Key

Developer identifier: project_browse_grants.grant_keyGrant Key identifies one Browse projects grant of one project. Parable computes it from project_key, holder_type and holder_value.

Enables: keep one row per project and holder across syncs.
Interpretation: The value is a digest, not a Jira identifier.

Holder Parameter

Developer identifier: project_browse_grants.holder_parameterHolder Parameter records the deprecated holder.parameter of the grant, such as a group name or an application key. Parable lifts it from the grant’s holder.

Enables: show a readable label for the holder.
Interpretation: A group name can change. Source permissions read holder_value, not this field.

Holder Type

Developer identifier: project_browse_grants.holder_typeHolder Type states who the grant is for. Parable lifts it from the grant’s holder.type.

Enables: decide how source permissions read the grant: a user, a group, every active user (applicationRole) or every reader (anyone). A project role grant reaches its actors through project_role_actors.
Interpretation: Reporter, assignee, project lead and custom field holders depend on each issue, and Parable gives them nothing, so such a grant fails closed.

Holder Value

Developer identifier: project_browse_grants.holder_valueHolder Value identifies the holder of the grant. Parable lifts it from the grant’s holder.value.

Enables: match a user grant to users.accountId, a group grant to groups.groupId, and a project role grant to its actors.
Interpretation: The meaning depends on holder_type. It is null for anyone. For source permissions, Parable marks this field as the subject of the grant.

Permission

Developer identifier: project_browse_grants.permissionPermission records the permission key of the grant. The tap keeps only BROWSE_PROJECTS.

Enables: confirm which permission each row grants.
Interpretation: Every row holds BROWSE_PROJECTS.

Project Key

Developer identifier: project_browse_grants.project_keyProject Key identifies the project the grant applies to. Parable copies it from the parent record in projects. Jira Cloud does not return this value with the record.

Enables: match each grant to its project.
Interpretation: For source permissions, Parable marks this field as the project the grant opens.

Project Role Actors

Developer identifier: project_role_actorsProject Role Actors contain the users and groups of each project role that holds Browse projects in a Jira Cloud project.

Enables: expand a Browse projects grant to a project role into the users and groups that hold the role in that project, so source permissions open the project to them.
Scope: Reads GET /rest/api/3/project/{project_key}/role/{role_id} for each project_browse_grants row whose holder type is projectRole, on each sync. The credential needs the Administer Jira global permission, or Administer projects on each project. One row per project, role, actor type and actor: the key is a digest of project_key, role_id, type and actor_id. A later complete read treats an actor that is absent as removed, so a person removed from the role loses the project after the next sync. Only people with All data access read this table.

Actor ID

Developer identifier: project_role_actors.actor_idActor ID identifies the user or group that holds the role. Parable lifts it from actorUser.accountId or actorGroup.groupId.

Enables: match a user actor to users.accountId and a group actor to groups.groupId.
Interpretation: The meaning depends on type. For source permissions, Parable marks this field as the subject of the grant.

Actor Key

Developer identifier: project_role_actors.actor_keyActor Key identifies one actor of one role in one project. Parable computes it from project_key, role_id, type and actor_id.

Enables: keep one row per project, role and actor across syncs.
Interpretation: The value is a digest, not a Jira identifier.

Display Name

Developer identifier: project_role_actors.displayNameDisplay Name records the display name of the user or group that holds the role.

Enables: show who an actor row names.
Interpretation: A name labels an actor but never joins two.

Actor Row ID

Developer identifier: project_role_actors.idActor Row ID identifies the role actor record in Jira.

Enables: trace a row to Jira’s role actor record.
Interpretation: The provider supplies id per actor of a role. Source permissions read actor_id, not this field.

Project Key

Developer identifier: project_role_actors.project_keyProject Key identifies the project in which the actor holds the role. Parable copies it from the parent record in project_browse_grants. Jira Cloud does not return this value with the record.

Enables: match each actor to its project.
Interpretation: For source permissions, Parable marks this field as the project the grant opens.

Role ID

Developer identifier: project_role_actors.role_idRole ID identifies the project role whose actor the row lists. Parable copies it from holder_value of the parent record in project_browse_grants. Jira Cloud does not return this value with the record.

Enables: group actors by role.
Interpretation: Role definitions are common to all projects. The actors are per project.

Actor Type

Developer identifier: project_role_actors.typeActor Type states whether the actor is a user or a group.

Enables: decide whether actor_id names a user or a group.
Interpretation: The provider supplies type per actor. A value other than the user and group actor types gives no access.

Projects

Developer identifier: projectsProjects contain Jira Cloud projects.

Enables: map Jira Cloud issues to their project containers and project metadata.
Scope: Reads every record from GET /rest/api/3/project/search on each sync. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

Archived

Developer identifier: projects.archivedArchived indicates whether the project is archived. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports archived as true or false.
Interpretation: The provider supplies archived as a boolean per jira cloud project record; false and missing are distinct when the field is optional. In Jira Cloud, archived is a condition on the work record, not a measure of a person’s performance.

Archived By

Developer identifier: projects.archivedByArchived By captures the user who archived the project. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported archived by value when describing their recorded state.
Interpretation: The provider supplies archivedBy per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Account ID

Developer identifier: projects.archivedBy.accountIdAccount ID identifies atlassian account ID of the user. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies accountId as a record-level identifier. Its values are not guaranteed to be unique.

Account Type

Developer identifier: projects.archivedBy.accountTypeAccount Type states type of the user account. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported account type value when describing their recorded state.
Interpretation: The provider supplies accountType per user summary record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Active

Developer identifier: projects.archivedBy.activeActive indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per user summary record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: projects.archivedBy.avatarUrlsAvatar URLs records avatar URLs for the user in various sizes. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by avatar urls on a user summary record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each user summary record. Availability still follows the provider’s permissions and retention.

16x16

Developer identifier: projects.archivedBy.avatarUrls.16x1616x16 records URL for the 16x16 pixel avatar. It retains the exact provider location for the referenced resource.

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

24x24

Developer identifier: projects.archivedBy.avatarUrls.24x2424x24 records URL for the 24x24 pixel avatar. It retains the exact provider location for the referenced resource.

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

32x32

Developer identifier: projects.archivedBy.avatarUrls.32x3232x32 records URL for the 32x32 pixel avatar. It retains the exact provider location for the referenced resource.

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

48x48

Developer identifier: projects.archivedBy.avatarUrls.48x4848x48 records URL for the 48x48 pixel avatar. It retains the exact provider location for the referenced resource.

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

Display Name

Developer identifier: projects.archivedBy.displayNameDisplay Name records display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

Developer identifier: projects.archivedBy.emailAddressEmail Address records email address of the user (if visible). It keeps the provider-reported person or account context attached to the record.

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

Self

Developer identifier: projects.archivedBy.selfSelf records REST API URL for this user resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a user summary record.
Interpretation: The provider supplies self as a URL or resource locator on each user summary record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: projects.archivedBy.timeZoneTime Zone records time zone of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

Enables: interpret dates, times, or localized text for projects using the recorded time zone.
Interpretation: The provider supplies timeZone as location or localization context per user summary record; it does not establish a person’s real-time physical location.

Archived Date

Developer identifier: projects.archivedDateArchived Date records the date when the project was archived.

Enables: place project records on a timeline by archived date.
Interpretation: The provider supplies archivedDate per jira cloud project record as a timestamp; a missing value means the time was not reported.

Avatar URLs

Developer identifier: projects.avatarUrlsAvatar URLs records URLs for the project avatar in various sizes. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by avatar urls on a jira cloud project record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each jira cloud project record. Availability still follows the provider’s permissions and retention.

Deleted

Developer identifier: projects.deletedDeleted indicates whether the project has been moved to the trash and is pending deletion. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports deleted as true or false.
Interpretation: The provider supplies deleted as a boolean per jira cloud project record; false and missing are distinct when the field is optional. In Jira Cloud, deleted is a condition on the work record, not a measure of a person’s performance.

Deleted By

Developer identifier: projects.deletedByDeleted By captures the user who deleted the project. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported deleted by value when describing their recorded state.
Interpretation: The provider supplies deletedBy per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Deleted Date

Developer identifier: projects.deletedDateDeleted Date records the date when the project was moved to the trash.

Enables: place project records on a timeline by deleted date.
Interpretation: The provider supplies deletedDate per jira cloud project record as a timestamp; a missing value means the time was not reported.

Description

Developer identifier: projects.descriptionDescription records project description text, may contain Atlassian Document Format or plain text. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each jira cloud project record.
Interpretation: The provider supplies description at jira cloud project granularity in the format stated by its description; omitted or redacted content remains unknown.

Entity ID

Developer identifier: projects.entityIdEntity ID identifies entity ID used for cross-product identification. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same entity ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies entityId as a record-level identifier. Its values are not guaranteed to be unique.

Expand

Developer identifier: projects.expandExpand records comma-separated list of expanded fields included in this response. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact expand when validating the configuration or technical definition of a jira cloud project record.
Interpretation: The provider supplies expand as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Developer identifier: projects.idID is the unique numeric identifier for the project (returned as string). It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Provider Attribute

Developer identifier: projects.insightProvider Attribute records insight information about the project’s recent activity. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: associate each jira cloud project record with the specific provider container named by provider attribute.
Interpretation: The provider returns insight as a nested object or reference; an absent value does not prove that no related object exists outside the credential’s visibility.

Last Issue Update Time

Developer identifier: projects.insight.lastIssueUpdateTimeLast Issue Update Time records the timestamp of the most recent issue update in the project. It anchors the named event or boundary on the record’s timeline.

Enables: place project records on a timeline by last issue update time and select the records within an explicit reporting window.
Interpretation: The provider supplies lastIssueUpdateTime per project insight record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Total Issue Count

Developer identifier: projects.insight.totalIssueCountTotal Issue Count reports the total number of issues in the project. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported total issue count for each project insight record.
Interpretation: The provider supplies totalIssueCount at project insight granularity as a count at one value per record; zero and missing are not interchangeable.

Is Private

Developer identifier: projects.isPrivateIs Private states whether the project is private from the perspective of the configured account, as Jira’s REST API documents the field. It is not an access rule for other people.

Enables: see how Jira classifies the project for the account that read it.
Interpretation: The configured account can see every project it reads, so the value does not say who else can browse the project. Source permissions read the project’s Browse projects grants from project_browse_grants and project_role_actors instead.

Issue Types

Developer identifier: projects.issueTypesIssue Types records issue types available in this project (present when expand includes issueTypes). It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: associate each jira cloud project record with the specific provider container named by issue types.
Interpretation: The provider returns issueTypes as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Description

Developer identifier: projects.issueTypes.descriptionDescription records description of the issue type. It keeps the exact text, label, or authored value needed to interpret the record.

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

Hierarchy Level

Developer identifier: projects.issueTypes.hierarchyLevelHierarchy Level states hierarchy level of this issue type.

Enables: filter and group project records by the Jira Cloud project issue type hierarchy level exposed by the nested object.
Interpretation: The provider supplies hierarchyLevel per project issue type record as a number; unknown and missing values must remain distinct.

Icon URL

Developer identifier: projects.issueTypes.iconUrlIcon URL records URL of the issue type icon. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by icon URL on a project issue type record.
Interpretation: The provider supplies iconUrl as a URL or resource locator on each project issue type record. Availability still follows the provider’s permissions and retention.

Developer identifier: projects.issueTypes.idID is the unique identifier for the issue type. It is the key of this nested record.

Enables: identify each project issue type record.
Interpretation: The provider supplies id at one value per project issue type record, and it is the key of this nested record.

Name

Developer identifier: projects.issueTypes.nameName states name of the issue type. It preserves the provider’s current classification of this record.

Enables: filter and group project records by the Jira Cloud project issue type name exposed by the nested object.
Interpretation: The provider supplies name per project issue type record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: projects.issueTypes.selfSelf records REST API URL for this issue type. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a project issue type record.
Interpretation: The provider supplies self as a URL or resource locator on each project issue type record. Availability still follows the provider’s permissions and retention.

Subtask

Developer identifier: projects.issueTypes.subtaskSubtask indicates whether this issue type represents subtasks. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports subtask as true or false.
Interpretation: The provider supplies subtask as a boolean per project issue type record; false and missing are distinct when the field is optional. In Jira Cloud, subtask is a condition on the work record, not a measure of a person’s performance.

Key

Developer identifier: projects.keyKey identifies short alphanumeric project key (e.g., PROJ) used in issue keys. It is the record key, so rows with the same value describe the same record.

Enables: identify each jira cloud project record across syncs.
Interpretation: The provider supplies key at one value per jira cloud project record, and it is the record key.

Landing Page Info

Developer identifier: projects.landingPageInfoLanding Page Info records information about the project landing page configuration. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact landing page info when validating the configuration or technical definition of a jira cloud project record.
Interpretation: The provider supplies landingPageInfo as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Board ID

Developer identifier: projects.landingPageInfo.boardIdBoard ID identifies board ID if the landing page is a board. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same board ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies boardId as a record-level identifier. Its values are not guaranteed to be unique.

Project Key

Developer identifier: projects.landingPageInfo.projectKeyProject Key identifies project key associated with the landing page. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same project key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies projectKey as a record-level identifier. Its values are not guaranteed to be unique.

Project Type

Developer identifier: projects.landingPageInfo.projectTypeProject Type states project type for the landing page. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported project type value when describing their recorded state.
Interpretation: The provider supplies projectType per project landing page info record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Queue ID

Developer identifier: projects.landingPageInfo.queueIdQueue ID identifies queue ID if the landing page is a service desk queue. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same queue ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies queueId as a record-level identifier. Its values are not guaranteed to be unique.

Simplified

Developer identifier: projects.landingPageInfo.simplifiedSimplified indicates whether the landing page uses simplified view. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports simplified as true or false.
Interpretation: The provider supplies simplified as a boolean per project landing page info record; false and missing are distinct when the field is optional. In Jira Cloud, simplified is a condition on the work record, not a measure of a person’s performance.

URL

Developer identifier: projects.landingPageInfo.urlURL records URL of the project landing page. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by URL on a project landing page info record.
Interpretation: The provider supplies url as a URL or resource locator on each project landing page info record. Availability still follows the provider’s permissions and retention.

Lead

Developer identifier: projects.leadLead captures the user designated as the project lead. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the jira cloud project record to the provider-reported person or account represented by lead.
Interpretation: The provider supplies lead as identity or attribution context on each jira cloud project record. In Jira Cloud, lead is attribution or membership context for the work record, not a measure of an individual’s performance.

Account ID

Developer identifier: projects.lead.accountIdAccount ID identifies atlassian account ID of the project lead. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same account ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies accountId as a record-level identifier. Its values are not guaranteed to be unique.

Account Type

Developer identifier: projects.lead.accountTypeAccount Type states type of the user account. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported account type value when describing their recorded state.
Interpretation: The provider supplies accountType per project lead record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Active

Developer identifier: projects.lead.activeActive indicates whether the user account is active. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per project lead record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: projects.lead.avatarUrlsAvatar URLs records avatar URLs for the project lead in various sizes. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by avatar urls on a project lead record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each project lead record. Availability still follows the provider’s permissions and retention.

Display Name

Developer identifier: projects.lead.displayNameDisplay Name records display name of the project lead. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the project lead record to the provider-reported person or account represented by display name.
Interpretation: The provider supplies displayName as identity or attribution context on each project lead record. In Jira Cloud, display name is attribution or membership context for the work record, not a measure of an individual’s performance.

Email Address

Developer identifier: projects.lead.emailAddressEmail Address records email address of the project lead (if visible). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the project lead record to the provider-reported person or account represented by email address.
Interpretation: The provider supplies emailAddress as identity or attribution context on each project lead record. In Jira Cloud, email address is attribution or membership context for the work record, not a measure of an individual’s performance.

Self

Developer identifier: projects.lead.selfSelf records REST API URL for this user resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a project lead record.
Interpretation: The provider supplies self as a URL or resource locator on each project lead record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: projects.lead.timeZoneTime Zone records time zone of the project lead. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

Enables: interpret dates, times, or localized text for projects using the recorded time zone.
Interpretation: The provider supplies timeZone as location or localization context per project lead record; it does not establish a person’s real-time physical location.

Name

Developer identifier: projects.nameName records display name of the project. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each jira cloud project record.
Interpretation: The provider supplies name at jira cloud project granularity in the format stated by its description; omitted or redacted content remains unknown.

Permissions

Developer identifier: projects.permissionsPermissions states permissions the current user has on this project. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported permissions attached to each jira cloud project record.
Interpretation: The provider supplies permissions at jira cloud project granularity. It describes provider-reported context and does not prove effective access beyond the returned record.

Can Edit

Developer identifier: projects.permissions.canEditCan Edit indicates whether the user can edit the project configuration. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports can edit as true or false.
Interpretation: The provider supplies canEdit as a boolean per project permission record; false and missing are distinct when the field is optional. In Jira Cloud, can edit is a condition on the work record, not a measure of a person’s performance.

Project Category

Developer identifier: projects.projectCategoryProject Category captures the category assigned to this project. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported project category value when describing their recorded state.
Interpretation: The provider supplies projectCategory per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Description

Developer identifier: projects.projectCategory.descriptionDescription records description of the project category. It keeps the exact text, label, or authored value needed to interpret the record.

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

Developer identifier: projects.projectCategory.idID is the unique identifier for the project category. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: projects.projectCategory.nameName states name of the project category. It preserves the provider’s current classification of this record.

Enables: filter and group project records by the Jira Cloud project category name exposed by the nested object.
Interpretation: The provider supplies name per project category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Self

Developer identifier: projects.projectCategory.selfSelf records REST API URL for this project category resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a project category record.
Interpretation: The provider supplies self as a URL or resource locator on each project category record. Availability still follows the provider’s permissions and retention.

Project Keys

Developer identifier: projects.projectKeysProject Keys records alternate project keys for this project (present when expand includes projectKeys). It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: associate each jira cloud project record with the specific provider container named by project keys.
Interpretation: The provider returns projectKeys as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Project Type Key

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

Enables: match project records to provider records that carry the same project type key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies projectTypeKey as a record-level identifier. Its values are not guaranteed to be unique.

Properties

Developer identifier: projects.propertiesProperties records arbitrary project properties as key-value metadata. It holds configured attributes whose keys and shapes can vary.

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. Check the keys in your Workspace’s data rather than assume a fixed set.

Retention Till Date

Developer identifier: projects.retentionTillDateRetention Till Date records the date until which a deleted project will be retained before permanent deletion. It anchors the named event or boundary on the record’s timeline.

Enables: place project records on a timeline by retention till date and select the records within an explicit reporting window.
Interpretation: The provider supplies retentionTillDate per jira cloud project record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Self

Developer identifier: projects.selfSelf records REST API URL for this project resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a jira cloud project record.
Interpretation: The provider supplies self as a URL or resource locator on each jira cloud project record. Availability still follows the provider’s permissions and retention.

Simplified

Developer identifier: projects.simplifiedSimplified indicates whether the project is a simplified (next-gen/team-managed) project. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports simplified as true or false.
Interpretation: The provider supplies simplified as a boolean per jira cloud project record; false and missing are distinct when the field is optional. In Jira Cloud, simplified is a condition on the work record, not a measure of a person’s performance.

Style

Developer identifier: projects.styleStyle states project style indicating management methodology (classic or next-gen). It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported style value when describing their recorded state.
Interpretation: The provider supplies style per jira cloud project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

URL

Developer identifier: projects.urlURL records URL to the project in the Jira web interface. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by URL on a jira cloud project record.
Interpretation: The provider supplies url as a URL or resource locator on each jira cloud project record. Availability still follows the provider’s permissions and retention.

UUID

Developer identifier: projects.uuidUUID is the unique UUID for the project. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same UUID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies uuid as a record-level identifier. Its values are not guaranteed to be unique.

Users

Developer identifier: usersUsers contain Jira Cloud users.

Enables: resolve Jira Cloud account identities referenced by issues, comments, and changes.
Scope: Reads every record from GET /rest/api/3/users/search on each sync. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

Account ID

Developer identifier: users.accountIdAccount ID is the unique Atlassian account identifier for the user. Primary key for cross-system identity resolution across Atlassian products. It is the record key, so rows with the same value describe the same record.

Enables: identify each jira cloud user record across syncs.
Interpretation: The provider supplies accountId at one value per jira cloud user record, and it is the record key.

Account Type

Developer identifier: users.accountTypeAccount Type states type of account: atlassian (normal user), app (service/bot account), or customer (Jira Service Management customer). It preserves the provider’s current classification of this record.

Enables: separate user records by the exact provider-reported account type value when describing their recorded state.
Interpretation: The provider supplies accountType per jira cloud user record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance. For source permissions, Parable treats a user as a member only when the value is atlassian. A customer or app account, or a missing or unknown value, is a guest.

Active

Developer identifier: users.activeActive indicates whether the user account is currently active. False indicates a deactivated account. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per jira cloud user record; false and missing are distinct when the field is optional. In Jira Cloud, active is a condition on the work record, not a measure of a person’s performance. For source permissions, Parable treats a user as active only when the value is true. A false, null or missing value makes the user inactive.

Application Roles

Developer identifier: users.applicationRolesApplication Roles states application roles assigned to the user. Only present when expanded. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported application roles attached to each jira cloud user record.
Interpretation: The provider supplies applicationRoles at jira cloud user granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, application roles describes access or membership, not a person’s performance.

Callback

Developer identifier: users.applicationRoles.callbackCallback records callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact callback when validating the configuration or technical definition of a application role list record.
Interpretation: The provider supplies callback as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Items

Developer identifier: users.applicationRoles.itemsItems captures the list of application role items. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported items attached to each 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 Cloud, items describes access or membership, not a person’s performance.

Default Groups

Developer identifier: users.applicationRoles.items.defaultGroupsDefault Groups states default groups for this application role. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported default groups attached to each application role item record.
Interpretation: The provider supplies defaultGroups at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, default groups describes access or membership, not a person’s performance.

Defined

Developer identifier: users.applicationRoles.items.definedDefined indicates whether this role is defined. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports defined as true or false.
Interpretation: The provider supplies defined as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, defined is a condition on the work record, not a measure of a person’s performance.

Groups

Developer identifier: users.applicationRoles.items.groupsGroups states groups associated with this application role. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported groups attached to each application role item record.
Interpretation: The provider supplies groups at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, groups describes access or membership, not a person’s performance.

Has Unlimited Seats

Developer identifier: users.applicationRoles.items.hasUnlimitedSeatsHas Unlimited Seats indicates whether this role has unlimited seats. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports has unlimited seats as true or false.
Interpretation: The provider supplies hasUnlimitedSeats as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, has unlimited seats is a condition on the work record, not a measure of a person’s performance.

Key

Developer identifier: users.applicationRoles.items.keyKey captures the key of the application role. It is needed to resolve references that repeat the same provider identifier.

Enables: match user records to provider records that carry the same key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies key as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: users.applicationRoles.items.nameName captures the display name of the application role. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported name attached to each application role item record.
Interpretation: The provider supplies name at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, name describes access or membership, not a person’s performance.

Number Of Seats

Developer identifier: users.applicationRoles.items.numberOfSeatsNumber Of Seats reports the number of seats for this application role. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported number of seats attached to each application role item record.
Interpretation: The provider supplies numberOfSeats at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, number of seats describes access or membership, not a person’s performance.

Platform

Developer identifier: users.applicationRoles.items.platformPlatform indicates whether this is a platform role. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports platform as true or false.
Interpretation: The provider supplies platform as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, platform is a condition on the work record, not a measure of a person’s performance.

Remaining Seats

Developer identifier: users.applicationRoles.items.remainingSeatsRemaining Seats reports the number of remaining seats for this application role. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported remaining seats attached to each application role item record.
Interpretation: The provider supplies remainingSeats at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, remaining seats describes access or membership, not a person’s performance.

Selected By Default

Developer identifier: users.applicationRoles.items.selectedByDefaultSelected By Default indicates whether this role is selected by default. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports selected by default as true or false.
Interpretation: The provider supplies selectedByDefault as a boolean per application role item record; false and missing are distinct when the field is optional. In Jira Cloud, selected by default is a condition on the work record, not a measure of a person’s performance.

User Count

Developer identifier: users.applicationRoles.items.userCountUser Count reports the number of users with this application role. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported user count attached to each application role item record.
Interpretation: The provider supplies userCount at application role item granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Cloud, user count describes access or membership, not a person’s performance.

User Count Description

Developer identifier: users.applicationRoles.items.userCountDescriptionUser Count Description reports human-readable description of the user count. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported user count description for each application role item record.
Interpretation: The provider supplies userCountDescription at application role item granularity as a count at one value per record; zero and missing are not interchangeable.

Max Results

Developer identifier: users.applicationRoles.max-resultsMax Results reports maximum number of results per page. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported max results for each application role list record.
Interpretation: The provider supplies max-results at application role list granularity as a count at one value per record; zero and missing are not interchangeable.

Paging Callback

Developer identifier: users.applicationRoles.pagingCallbackPaging Callback records paging callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact paging callback when validating the configuration or technical definition of a application role list record.
Interpretation: The provider supplies pagingCallback as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Size

Developer identifier: users.applicationRoles.sizeSize reports the number of application roles returned in the current page. It counts the items in the list that Jira returned.

Enables: compare the number of returned roles with Max Results, the most that Jira returns per page.
Interpretation: The provider supplies size as an integer item count, not bytes; zero denotes an empty page while missing means page size was not reported.

App Type

Developer identifier: users.appTypeApp Type states app account subtype when accountType is app (service, agent, or unknown). It preserves the provider’s current classification of this record.

Enables: separate user records by the exact provider-reported app type value when describing their recorded state.
Interpretation: The provider supplies appType per jira cloud user record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Cloud, this value describes the work record, not a person’s performance.

Avatar URLs

Developer identifier: users.avatarUrlsAvatar URLs records URLs for the user’s avatar images in various sizes. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by avatar urls on a jira cloud user record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each jira cloud user record. Availability still follows the provider’s permissions and retention.

16x16

Developer identifier: users.avatarUrls.16x1616x16 records URL for the 16x16 pixel avatar image. It retains the exact provider location for the referenced resource.

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

24x24

Developer identifier: users.avatarUrls.24x2424x24 records URL for the 24x24 pixel avatar image. It retains the exact provider location for the referenced resource.

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

32x32

Developer identifier: users.avatarUrls.32x3232x32 records URL for the 32x32 pixel avatar image. It retains the exact provider location for the referenced resource.

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

48x48

Developer identifier: users.avatarUrls.48x4848x48 records URL for the 48x48 pixel avatar image. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by 48x48 on a avatar url record.
Interpretation: The provider supplies 48x48 as a URL or resource locator on each avatar url record. Availability still follows the provider’s permissions and retention. Parable uses this image as the person’s photo.

Display Name

Developer identifier: users.displayNameDisplay Name records user’s display name as shown in the Jira UI. It keeps the provider-reported person or account context attached to the record.

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

Email Address

Developer identifier: users.emailAddressEmail Address records user’s email address. May be absent if hidden by the user’s privacy settings. It keeps the provider-reported person or account context attached to the record.

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

Expand

Developer identifier: users.expandExpand records comma-separated list of expanded properties included in this response. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact expand when validating the configuration or technical definition of a jira cloud user record.
Interpretation: The provider supplies expand as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Groups

Developer identifier: users.groupsGroups records groups the user belongs to. Only present when expanded. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: associate each jira cloud user record with the specific provider container named by groups.
Interpretation: The provider returns groups as a nested object or reference; an absent value does not prove that no related object exists outside the credential’s visibility.

Callback

Developer identifier: users.groups.callbackCallback records callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact callback when validating the configuration or technical definition of a group list record.
Interpretation: The provider supplies callback as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Items

Developer identifier: users.groups.itemsItems captures the list of group items. It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: enumerate the nested items records contained by each group list record.
Interpretation: The provider returns items as a list; an absent value does not prove that no related object exists outside the credential’s visibility.

Group ID

Developer identifier: users.groups.items.groupIdGroup ID captures the unique identifier of the group. It is needed to resolve references that repeat the same provider identifier.

Enables: match user records to provider records that carry the same group ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies groupId as a record-level identifier. Its values are not guaranteed to be unique.

Name

Developer identifier: users.groups.items.nameName captures the name of the group. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each group item record.
Interpretation: The provider supplies name at group item granularity in the format stated by its description; omitted or redacted content remains unknown.

Self

Developer identifier: users.groups.items.selfSelf records REST API URL for this group resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a group item record.
Interpretation: The provider supplies self as a URL or resource locator on each group item record. Availability still follows the provider’s permissions and retention.

Max Results

Developer identifier: users.groups.max-resultsMax Results reports maximum number of results per page. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported max results for each group list record.
Interpretation: The provider supplies max-results at group list granularity as a count at one value per record; zero and missing are not interchangeable.

Paging Callback

Developer identifier: users.groups.pagingCallbackPaging Callback records paging callback metadata. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact paging callback when validating the configuration or technical definition of a group list record.
Interpretation: The provider supplies pagingCallback as configuration or technical metadata; consumers must preserve the exact syntax and documented vocabulary.

Size

Developer identifier: users.groups.sizeSize reports the number of groups returned in the current page. It counts the items in the list that Jira returned.

Enables: compare the number of returned groups with Max Results, the most that Jira returns per page.
Interpretation: The provider supplies size as an integer item count, not bytes; zero denotes an empty page while missing means page size was not reported.

Locale

Developer identifier: users.localeLocale records user’s locale setting as a BCP 47 language tag (e.g., en_US). It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

Enables: interpret dates, times, or localized text for users using the recorded locale.
Interpretation: The provider supplies locale as location or localization context per jira cloud user record; it does not establish a person’s real-time physical location.

Self

Developer identifier: users.selfSelf records REST API URL for this user resource. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by self on a jira cloud user record.
Interpretation: The provider supplies self as a URL or resource locator on each jira cloud user record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: users.timeZoneTime Zone records user’s configured IANA timezone (e.g., America/New_York). It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

Enables: interpret dates, times, or localized text for users using the recorded time zone.
Interpretation: The provider supplies timeZone as location or localization context per jira cloud user record; it does not establish a person’s real-time physical location.

​Jira Cloud setup

​Data streams

​Jira

​What You’ll Need

​Prerequisites

​Setup

​What You’ll Need

​Prerequisites

​Setup

​Jira

​Who reads Jira Cloud rows

Jira Cloud setup

Data streams

Jira

What You’ll Need

Prerequisites

Setup

What You’ll Need

Prerequisites

Setup

Jira

Who reads Jira Cloud rows