Jira Data Center

Sync issues, comments, worklogs, projects, users, and groups from Jira Data Center (self-hosted). Each issue includes its change history.

Overview
Setup Guide
Permissions
Troubleshooting

Connect Parable to Jira Server or Data Center using Personal Access Tokens (PATs) for secure API access without exposing passwords.

Feature	Jira Server	Jira Cloud
Auth	PAT or Basic	API Token + Basic
Base URL	Custom	`*.atlassian.net`
Audit Logs	Limited	Full

Tip: Rate Limits: Jira Server enforces rate limits of varies by server configuration. Parable waits and tries again when Jira limits requests, so the first sync of a large dataset can take longer.

Data streams

This Provider Plugin defines 10 data streams.

Stream	Description	Sync
`projects`	Jira Data Center projects	full
`users`	Jira Data Center users	full
`groups`	Jira Data Center groups	full
`group_members`	Members of each Jira Data Center 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
`project_role_users`	User key of each user actor of a project role that holds Browse Projects	full
`issues`	Jira Data Center issues, with the change history of each issue	incremental
`comments`	Issue comments including author and updateAuthor user objects	full
`worklogs`	Issue worklogs including author, time spent and visibility (off by default)	full

Personal access token

What You’ll Need

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

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

Jira Administrator: create the Personal Access Token as an account with the Jira Administrators global permission. The project_browse_grants, project_role_actors and project_role_users streams read each project’s permission scheme and project roles, and Jira returns them only to an administrator. The groups and group_members streams need the Browse users and groups global permission, which administrators hold.
Browse Projects on every project you want to sync
The jira.ajax.autocomplete.limit system property set above the number of groups on your instance. Jira lists at most that many groups to the groups stream, and the members of a group past the limit do not get the group’s access in Parable.
Personal Access Tokens enabled on your instance (Jira 8.14+)
Network access to your Jira Server

Step 1: Access Profile Settings

Log in to your Jira Server instance
Click your avatar → Profile
Navigate to Personal Access Tokens

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

Step 2: Create Personal Access Token

Click Create token
Enter name: Parable Integration
Set expiration (optional)
Click Create

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

Step 3: Note Your Base URL

Your Jira Server URL format:

https://jira.yourcompany.com

Step 4: Enter values in the form

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

Endpoint	Jira permission
`/rest/api/2/project`	Browse Projects
`/rest/api/2/search`, `/rest/api/2/issue/{id}/comment`, `/rest/api/2/issue/{id}/worklog`	Browse Projects
`/rest/api/2/user/search`, `/rest/api/2/user`	Browse users and groups
`/rest/api/2/groups/picker`, `/rest/api/2/group/member`	Browse users and groups
`/rest/api/2/project/{key}/permissionscheme`, `/rest/api/2/project/{key}/role/{id}`	Jira Administrators

An administrator’s token holds every permission in this table. Without the Jira Administrators global permission, 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 Data Center projects, issues, comments and worklogs.

Who reads Jira Data Center rows

In Jira Data Center, the permission scheme of a project decides who browses it. Its Browse Projects permission names users, groups, project roles, every user of an application, or anyone. An issue security level hides an issue from people who are not in the level, and the visibility of a comment or a worklog limits it to a group or a project role.Parable reads Jira Data Center with an administrator’s token, so it reads every project the token 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 Data Center 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, every active Jira user
`issues`	The people who read the issue’s project. An issue with a security level reads only for people with All data access.
`comments`, `worklogs`	The people who read the issue. A comment or worklog restricted to a group or a project role reads only for people with All data access.
`users`, `groups`, `group_members`	Every active Jira user
`project_browse_grants`, `project_role_actors`, `project_role_users`	Only people with All data access

Parable matches each member to their Jira user by the email they sign in with. A member whose Jira user has no email reads no Jira Data Center row until an administrator confirms the link between the member and the Jira account.
When Jira deactivates or deletes a user, that member reads no Jira Data Center row after the next sync of users. A user whose active state Jira does not return also reads no row. 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, project_role_actors and project_role_users, 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 or worklog’s group or role, so those records read only for people with All data access. An application grant admits every active Jira user, also a person without that application, such as a Jira Service Management portal customer. Jira lists at most as many groups as the jira.ajax.autocomplete.limit system property allows: the members of a group past that limit do not get the group’s access. 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 and worklogs streams read them with their visibility.

Comments

Developer identifier: commentsComments contain Jira Data Center 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/2/issue/{id}/comment for each issue that the issues sync reads: one request per 100 comments of each changed issue. Results contain only Jira records visible to the configured account. 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 comment record to the provider-reported actor represented by author.
Interpretation: The provider supplies author as identity or attribution context on each comment record. In Jira Data Center, author is attribution or membership context for the work record, not a measure of an individual’s performance.

Account ID

Developer identifier: comments.author.accountIdAccount ID is the unique account ID (Atlassian account ID, if applicable). It is needed to resolve references that repeat the same provider identifier.

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

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 issue records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per user record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: comments.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 record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each user record. Availability still follows the provider’s permissions and retention.

16x16

Developer identifier: comments.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: comments.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: comments.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: comments.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: comments.author.displayNameDisplay Name records full display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

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

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

Key

Developer identifier: comments.author.keyKey identifies user key (unique identifier in Jira Data Center). It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: comments.author.nameName records username / login name. It keeps the exact text, label, or authored value needed to interpret the record.

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

Self

Developer identifier: comments.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 record.
Interpretation: The provider supplies self as a URL or resource locator on each user record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: comments.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 record; it does not establish a person’s real-time physical location.

Body

Developer identifier: comments.bodyBody records comment body text. It keeps the exact text, label, or authored value needed to interpret the record.

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

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 issue records on a timeline by created and select the records within an explicit reporting window.
Interpretation: The provider supplies created per comment record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

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 ID of the comment. It is the record key, so rows with the same value describe the same record.

Enables: identify each jira data center comment record across syncs.
Interpretation: The provider supplies id at one value per 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.

Enables: match comment records to the issue they belong to.
Interpretation: For source permissions, a comment inherits the readers of this issue unless it has a visibility.

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.

Enables: show which issue a comment belongs to.
Interpretation: An issue that moves to another project gets a new key, so match on issue_id.

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 comment record.
Interpretation: The provider supplies self as a URL or resource locator on each comment record. Availability still follows the provider’s permissions and retention.

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 comment record to the provider-reported actor represented by update author.
Interpretation: The provider supplies updateAuthor as identity or attribution context on each comment record. In Jira Data Center, update author is attribution or membership context for the work record, not a measure of an individual’s performance.

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 issue records on a timeline by updated and select the records within an explicit reporting window.
Interpretation: The provider supplies updated per comment record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Visibility

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

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

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 record.
Interpretation: The provider supplies type at visibility granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Data Center, type 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 users that belong to each Jira Data Center 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/2/group/member for each group in groups on each sync, inactive users included. Jira returns the members of the group and of its subgroups as one flat list. 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 user: the key is a digest of group_name and key.

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 Name

Developer identifier: group_members.group_nameGroup Name identifies the group of the membership. Parable copies it from the parent record in groups. Jira Data Center 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.

User Key

Developer identifier: group_members.keyUser Key identifies the member’s Jira user. Unlike the username, it does not change when the user is renamed.

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

Membership Key

Developer identifier: group_members.membership_keyMembership Key identifies one membership of one user in one group. Parable computes it from group_name and key.

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

Username

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

Enables: show which login a membership names.
Interpretation: An administrator can rename a user, so source permissions read key, not this field.

Groups

Developer identifier: groupsGroups contain the Jira Data Center groups.

Enables: list the groups whose members group_members reads, so source permissions give each member the tokens of the Browse Projects grants and project roles that name the group.
Scope: Reads GET /rest/api/2/groups/picker with no query on each sync. Jira has no endpoint that lists every group, and the picker returns at most the number of groups that the system property jira.ajax.autocomplete.limit allows. A group past that limit has no members in Parable, so its grants admit nobody: this fails closed. A later complete read treats a previously seen group that is absent as removed.

Name

Developer identifier: groups.nameName identifies the group. Jira Data Center has no group ID, so the name is the record key.

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

Issues

Developer identifier: issuesIssues contain Jira Data Center issues via JQL search (v2 API, includes embedded changelogs).

Enables: report issue content, state, assignment, and embedded change history as work-record context.
Scope: Reads the records that changed since the previous sync from POST /rest/api/2/search. 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 and worklogs taps read them with their visibility. has_security_level is true when the issue has an issue security level.

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

Changelog

Developer identifier: issues.changelogChangelog records change history for the issue (present when expand=changelog). It preserves the containing or referenced object needed to reconstruct the provider relationship.

Enables: enumerate the nested changelog records contained by each jira data center issue record.
Interpretation: The provider returns changelog as a nested object or reference; 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 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 change. It keeps the provider-reported person or account context attached to the record.

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

Account ID

Developer identifier: issues.changelog.histories.author.accountIdAccount ID is the unique account ID (Atlassian account ID, if applicable). It is needed to resolve references that repeat the same provider identifier.

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

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 record; false and missing are distinct when the field is optional. In Jira Data Center, 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 record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each user record. Availability still follows the provider’s permissions and retention.

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 full display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

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

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

Key

Developer identifier: issues.changelog.histories.author.keyKey identifies user key (unique identifier in Jira Data Center). It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: issues.changelog.histories.author.nameName records username / login name. It keeps the exact text, label, or authored value needed to interpret the record.

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

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 record.
Interpretation: The provider supplies self as a URL or resource locator on each user record. Availability still follows the provider’s permissions and retention.

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 record; it does not establish a person’s real-time physical location.

Created

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

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

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

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

Items

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

Enables: enumerate the nested items records contained by each change history record.
Interpretation: The provider returns items as a list; 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 human-readable name of the field that changed. It keeps the exact text, label, or authored value needed to interpret the record.

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

Field ID

Developer identifier: issues.changelog.histories.items.fieldIdField ID identifies machine ID of the field (e.g., status, customfield_10001). It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same field ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies fieldId as a record-level identifier. 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/key (for reference fields). It preserves the recorded before, after, or contextual value needed to explain a change event.

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

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/key (for reference fields). It preserves the recorded before, after, or contextual value needed to explain a change event.

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

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 record.
Interpretation: The provider supplies maxResults at changelog 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 zero-based 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 the position of the first returned entry, 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 record.
Interpretation: The provider supplies total at changelog 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 data center 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 standard and custom fields on 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, the original estimate, and completion percentage for the issue and its subtasks. It keeps the rollup separate from issue-only progress.

Enables: compare aggregate spent time with the estimate and identify issue trees that are incomplete or overrunning plan.
Interpretation: The provider supplies aggregateprogress as a nested object whose time values are seconds and whose percent value expresses completion; absence means no rollup was reported.

Percent

Developer identifier: issues.fields.aggregateprogress.percentPercent reports the issue’s completion percentage. It summarizes the relationship between time spent and the original estimate.

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

Progress

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

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

Total

Developer identifier: issues.fields.aggregateprogress.totalTotal reports the total value (original estimate in seconds). It preserves the elapsed interval reported for this record.

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

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 currently assigned to the issue. It keeps the provider-reported person or account context attached to the record.

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

Attachment

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

Enables: enumerate the nested attachment records contained by each issue field record.
Interpretation: The provider returns attachment as a list; 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 record to the provider-reported actor represented by author.
Interpretation: The provider supplies author as identity or attribution context on each attachment record. In Jira Data Center, author is attribution or membership context for the work record, not a measure of an individual’s performance.

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 record.
Interpretation: The provider supplies content at attachment 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 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 original filename of the attachment. It keeps the exact text, label, or authored value needed to interpret the record.

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

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

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. 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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 record.
Interpretation: The provider supplies self as a URL or resource locator on each attachment record. Availability still follows the provider’s permissions and retention.

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 of the attachment thumbnail (if applicable). It retains the exact provider location for the referenced resource.

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

Closed Sprints

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

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

Completion Date

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

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

End Date

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

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

Goal

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

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

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

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

Name

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

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

Origin Board ID

Developer identifier: issues.fields.closedSprints.originBoardIdOrigin Board ID is the ID of the board the sprint originated from. It is needed to resolve references that repeat the same provider identifier.

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

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 record.
Interpretation: The provider supplies self as a URL or resource locator on each sprint record. Availability still follows the provider’s permissions and retention.

Start Date

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

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

State

Developer identifier: issues.fields.closedSprints.stateState states state of the sprint (future, active, closed). It preserves the provider’s current classification of this record.

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

Components

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

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

Assignee Type

Developer identifier: issues.fields.components.assigneeTypeAssignee Type states default assignee type for the component. It preserves the provider’s current classification of this record.

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

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

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

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

Lead

Developer identifier: issues.fields.components.leadLead records component lead user. It keeps the provider-reported person or account context attached to the record.

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

Name

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

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

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 record.
Interpretation: The provider supplies self as a URL or resource locator on each component record. Availability still follows the provider’s permissions and retention.

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 originally created the issue record. It keeps the provider-reported person or account context attached to the record.

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

Custom Fields

Developer identifier: issues.fields.customFieldsCustom Fields records arbitrary custom fields (customfield_NNNNN) not explicitly modeled. It holds configured attributes whose keys and shapes can vary.

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

Description

Developer identifier: issues.fields.descriptionDescription records full description body of the issue (wiki markup or plain text). It keeps the exact text, label, or authored value needed to interpret the record.

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

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 information for the issue. It preserves the provider’s current classification of this record.

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

Epic

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

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

Color

Developer identifier: issues.fields.epic.colorColor records color configuration of the epic. It preserves the provider’s visual treatment for the represented object.

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

Key

Developer identifier: issues.fields.epic.color.keyKey identifies color key identifier (e.g., color_1, color_2). It is needed to resolve references that repeat the same provider identifier.

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

Done

Developer identifier: issues.fields.epic.doneDone indicates whether the epic is marked as done. It preserves the provider-reported yes-or-no condition for this record.

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

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

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

Key

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

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

Name

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

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

Self

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

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

Summary

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

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

Fix Versions

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

Enables: expand the nested fix versions object into its declared child fields for each issue field record.
Interpretation: The provider returns fixVersions as a list; 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 the version is archived. It preserves the provider-reported yes-or-no condition for this record.

Enables: select issue records for which the provider reports archived as true or false.
Interpretation: The provider supplies archived as a boolean per version record; false and missing are distinct when the field is optional. In Jira Data Center, archived is a condition on the work record, not 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 record.
Interpretation: The provider supplies description at version granularity in the format stated by its description; omitted or redacted content remains unknown.

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

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

Name

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

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

Released

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

Enables: select issue records for which the provider reports released as true or false.
Interpretation: The provider supplies released as a boolean per version record; false and missing are distinct when the field is optional. In Jira Data Center, released is a condition on the work record, not 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 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 record.
Interpretation: The provider supplies self as a URL or resource locator on each version record. Availability still follows the provider’s permissions and retention.

Start Date

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

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

Flagged

Developer identifier: issues.fields.flaggedFlagged indicates whether the issue is flagged/impediment. It preserves the provider-reported yes-or-no condition for this record.

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

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 ID of the issue link. It is needed to resolve references that repeat the same provider identifier.

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. 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 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.

Fields

Developer identifier: issues.fields.issuelinks.inwardIssue.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.issuelinks.inwardIssue.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 Data Center, this value describes the work record, not a person’s performance.

Avatar ID

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.issuetype.avatarIdAvatar ID identifies avatar ID for the issue type. It is needed to resolve references that repeat the same provider identifier.

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

Description

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies description at issue type granularity in the format stated by its description; omitted or redacted content remains unknown.

Icon URL

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies iconUrl as a URL or resource locator on each issue type record. Availability still follows the provider’s permissions and retention.

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.issuetype.idID is the unique ID of the issue type. It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.issuetype.nameName states display name (e.g., Bug, Story, Task, Epic, Sub-task). It preserves the provider’s current classification of this record.

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

Self

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies self as a URL or resource locator on each issue type record. Availability still follows the provider’s permissions and retention.

Subtask

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

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

Priority

Developer identifier: issues.fields.issuelinks.inwardIssue.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 Data Center, this value describes the work record, not a person’s performance.

Description

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

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

Icon URL

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies iconUrl as a URL or resource locator on each priority record. Availability still follows the provider’s permissions and retention.

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.priority.idID is the unique ID of the priority. It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.priority.nameName states display name of the priority (e.g., Highest, High, Medium, Low, Lowest). It preserves the provider’s current classification of this record.

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

Self

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies self as a URL or resource locator on each priority record. Availability still follows the provider’s permissions and retention.

Status

Developer identifier: issues.fields.issuelinks.inwardIssue.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 Data Center, this value describes the work record, not a person’s performance.

Description

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies description at status granularity in the format stated by its description; omitted or redacted content remains unknown.

Icon URL

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies iconUrl as a URL or resource locator on each status record. Availability still follows the provider’s permissions and retention.

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.status.idID is the unique ID of the status. It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: issues.fields.issuelinks.inwardIssue.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 Data Center status name exposed by the nested object.
Interpretation: The provider supplies name per status record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies self as a URL or resource locator on each status record. Availability still follows the provider’s permissions and retention.

Status Category

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.status.statusCategoryStatus Category states high-level category of the status. It preserves the provider’s current classification of this record.

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

Color Name

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

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

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.status.statusCategory.idID is the unique ID of the status category. It is needed to resolve references that repeat the same provider identifier.

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

Key

Developer identifier: issues.fields.issuelinks.inwardIssue.fields.status.statusCategory.keyKey is the key of the status category (e.g., new, indeterminate, done). It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: issues.fields.issuelinks.inwardIssue.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 Data Center status category name exposed by the nested object.
Interpretation: The provider supplies name per status category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, this value describes the work record, not a person’s performance.

Self

Developer identifier: issues.fields.issuelinks.inwardIssue.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 record.
Interpretation: The provider supplies self as a URL or resource locator on each status category record. Availability still follows the provider’s permissions and retention.

Summary

Developer identifier: issues.fields.issuelinks.inwardIssue.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.issuelinks.inwardIssue.idID is the unique numeric ID of the referenced issue. It is needed to resolve references that repeat the same provider identifier.

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

Key

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

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

Self

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

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 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 issue link. It retains the exact provider location for the referenced resource.

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

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 record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, this value describes the work record, not a person’s performance.

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

Enables: match issue records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. 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 record.
Interpretation: The provider supplies inward at issue link type 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 (e.g., Blocks, Cloners, Duplicate). It keeps the exact text, label, or authored value needed to interpret the record.

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

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 record.
Interpretation: The provider supplies outward at issue link type 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 record.
Interpretation: The provider supplies self as a URL or resource locator on each issue link type record. Availability still follows the provider’s permissions and retention.

Issuetype

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

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

Progress

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

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

Project

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

Enables: associate each issue field record with the specific provider container named by project.
Interpretation: The provider returns project as a nested object or reference; 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 record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each project record. Availability still follows the provider’s permissions and retention.

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

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

Key

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

Enables: match issue records to provider records that carry the same key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies key as a record-level identifier. 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 record.
Interpretation: The provider supplies name at project 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 the project belongs to. It preserves the provider’s current classification of this record.

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

Description

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

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

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

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

Name

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

Enables: filter and group issue records by the Jira Data Center project category name exposed by the nested object.
Interpretation: The provider supplies name per project category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 project category. It retains the exact provider location for the referenced resource.

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

Project Type Key

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

Enables: match issue records to provider records that carry the same project type key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies projectTypeKey as a record-level identifier. 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 record.
Interpretation: The provider supplies self as a URL or resource locator on each project record. Availability still follows the provider’s permissions and retention.

Reporter

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

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

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 Data Center, 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 record.
Interpretation: The provider supplies description at resolution granularity in the format stated by its description; omitted or redacted content remains unknown.

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

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

Name

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

Enables: filter and group issue records by the Jira Data Center resolution name exposed by the nested object.
Interpretation: The provider supplies name per resolution record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 record.
Interpretation: The provider supplies self as a URL or resource locator on each resolution record. Availability still follows the provider’s permissions and retention.

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 the issue. It preserves the provider’s current classification of this record.

Enables: separate issue records by the exact provider-reported security value when describing their recorded state.
Interpretation: The provider supplies security per issue field record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 record.
Interpretation: The provider supplies description at security level granularity in the format stated by its description; omitted or redacted content remains unknown.

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

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

Name

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

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

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 record.
Interpretation: The provider supplies self as a URL or resource locator on each security level record. Availability still follows the provider’s permissions and retention.

Sprint

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

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

Statuscategorychangedate

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

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

Story Points

Developer identifier: issues.fields.storyPointsStory Points records story point 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 one-line summary/title of the issue. It keeps the exact text, label, or authored value needed to interpret the record.

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

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 2d 4h; 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 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 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 time spent. It preserves the elapsed interval reported for this record.

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

Time Spent Seconds

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

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

Updated

Developer identifier: issues.fields.updatedUpdated records the timestamp of the last modification to the issue. It anchors the named event or boundary on the record’s timeline.

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

Versions

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

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

Votes

Developer identifier: issues.fields.votesVotes records vote count and self-vote status. It retains the exact provider location for the referenced resource.

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

Has Voted

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

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

Self

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

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

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 vote record.
Interpretation: The provider supplies votes at vote granularity as a count at one value per record; zero and missing are not interchangeable.

Watches

Developer identifier: issues.fields.watchesWatches records watch count and self-watch status. It retains the exact provider location for the referenced resource.

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

Is Watching

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

Enables: separate issues the current user watches from those they do not.
Interpretation: The provider supplies isWatching as a boolean per watches record; false and missing are distinct. It is a condition on the issue, not a measure of a person’s performance.

Self

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

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

Watch Count

Developer identifier: issues.fields.watches.watchCountWatch Count reports the number of users watching the issue. It preserves the audience count in the watcher summary.

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

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 for which the ratio does not apply.
Interpretation: The provider supplies workratio as an integer percentage and uses -1 when the ratio is not applicable; -1, zero, and missing have different meanings.

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 ID of the issue. It is the record key, so rows with the same value describe the same record.

Enables: identify each jira data center issue record across syncs.
Interpretation: The provider supplies id at one value per jira data center 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.

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

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 data center issue record.
Interpretation: The provider supplies self as a URL or resource locator on each jira data center issue record. Availability still follows the provider’s permissions and retention.

Project Browse Grants

Developer identifier: project_browse_grantsProject Browse Grants contain the Browse Projects grants of the permission scheme that each Jira Data Center 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 worklogs to the same people Jira does. A grant to a project role is expanded into its actors by project_role_actors and project_role_users.
Scope: Reads GET /rest/api/2/project/{key}/permissionscheme with expand=permissions,user,group,projectRole for each project in projects on each sync and keeps only the BROWSE_PROJECTS grants. The Personal Access Token must belong to a Jira administrator (the Jira Administrators global permission): Jira refuses this read for other accounts, and the project then holds no token, so only people with All data access read it. One row per project and holder: the key is a digest of project_key, holder_type, holder_parameter and holder_id. 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, holder_parameter and holder_id.

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

Holder ID

Developer identifier: project_browse_grants.holder_idHolder ID identifies the holder of the grant. Parable lifts the user key from the expanded holder.user of a user grant, and holder.parameter for every other holder type.

Enables: match a user grant to users.key and a group grant to groups.name.
Interpretation: The meaning depends on holder_type. It is null for anyone, and for a user grant whose expanded user Jira did not return, which then gives nothing. For source permissions, Parable marks this field as the subject of the grant.

Holder Parameter

Developer identifier: project_browse_grants.holder_parameterHolder Parameter records holder.parameter of the grant. Parable lifts it from the grant’s holder.

Enables: show the holder as Jira names it, and read the role ID of a project role grant.
Interpretation: Jira documents a user holder’s parameter as a user ID without saying whether it is the user key or the username, so source permissions read a user grant from holder_id.

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 and project_role_users.
Interpretation: Reporter, assignee, project lead and custom field holders depend on each issue, and Parable gives them nothing, so such a grant fails closed. A holder type that the map does not name also gives nothing.

Holder Username

Developer identifier: project_browse_grants.holder_user_nameHolder Username records the login name of a user holder. Parable lifts it from the expanded holder.user.

Enables: show which login a user grant names.
Interpretation: An administrator can rename a user, so source permissions read holder_id, not this field.

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 Data Center 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 Data Center project.

Enables: expand a Browse Projects grant to a project role into the groups that hold the role in that project, so source permissions open the project to their members. A user actor carries its username, so project_role_users reads its user key.
Scope: Reads GET /rest/api/2/project/{project_key}/role/{role_id} for each project_browse_grants row whose holder type is projectRole, on each sync. The Personal Access Token must belong to a Jira administrator (the Jira Administrators global permission): Jira refuses this read for other accounts, and the project then holds no token, so only people with All data access read it. One row per project, role, actor type and actor name: the key is a digest of project_key, role_id, type and name. A later complete read treats an actor that is absent as removed, so a person or group removed from the role loses the project after the next sync. Only people with All data access read this table.

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

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 name, not this field.

Actor Name

Developer identifier: project_role_actors.nameActor Name identifies the user or group that holds the role.

Enables: match a group actor to groups.name, and look up the user key of a user actor in project_role_users.
Interpretation: Jira takes usernames for user actors, so a user actor’s name is not a user key and gives no access here. For source permissions, Parable marks this field as the subject of a group actor’s grant.

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 Data Center 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_parameter of the parent record in project_browse_grants. Jira Data Center 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 name names a user or a group.
Interpretation: A group actor gives the project to the group. A user actor gives nothing here: project_role_users gives the project to the user’s key. Any other value gives no access.

Project Role Users

Developer identifier: project_role_usersProject Role Users contain the user key of each user actor of a project role that holds Browse Projects in a Jira Data Center project.

Enables: open a project to the users that hold a role with Browse Projects in it. Jira names a user actor by username, and users keys on the user key, so this tap looks the key up.
Scope: Reads GET /rest/api/2/user?username={actor_name} for each project_role_actors row whose type is atlassian-user-role-actor, on each sync: one request per user actor of each role grant of each project. A user that Jira does not find is recorded as a refused parent and gives nothing. One row per project, role and user: the key is a digest of project_key, role_id and key. A later complete read treats a row that is absent as removed, so a user removed from the role loses the project after the next sync. Only people with All data access read this table.

Active

Developer identifier: project_role_users.activeActive indicates whether the user’s account is active.

Enables: see inactive users that still hold a role.
Interpretation: The users record of the account decides whether the account gives tokens.

Actor Username

Developer identifier: project_role_users.actor_nameActor Username records the username that the role actor names. Parable copies it from name of the parent record in project_role_actors and looks the user up by it.

Enables: trace a row to its role actor.
Interpretation: An administrator can rename a user, so source permissions read key, not this field.

Display Name

Developer identifier: project_role_users.displayNameDisplay Name records the user’s display name.

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

User Key

Developer identifier: project_role_users.keyUser Key identifies the Jira user that holds the role. Unlike the username, it does not change when the user is renamed.

Enables: match the role holder to the users record with the same key.
Interpretation: For source permissions, Parable marks this field as the user the grant is for.

Username

Developer identifier: project_role_users.nameUsername records the user’s current login name.

Enables: show which login holds the role.
Interpretation: Source permissions read key, not this field.

Project Key

Developer identifier: project_role_users.project_keyProject Key identifies the project in which the user holds the role. Parable copies it from the parent record in project_role_actors. Jira Data Center does not return this value with the record.

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

Role ID

Developer identifier: project_role_users.role_idRole ID identifies the project role that the user holds. Parable copies it from the parent record in project_role_actors.

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

Role User Key

Developer identifier: project_role_users.role_user_keyRole User Key identifies one user holding one role in one project. Parable computes it from project_key, role_id and key.

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

Projects

Developer identifier: projectsProjects contain Jira Data Center projects.

Enables: map Jira Data Center issues to their self-hosted project containers.
Scope: Reads every record from GET /rest/api/2/project 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 data center project record; false and missing are distinct when the field is optional. In Jira Data Center, archived is a condition on the work record, not a measure of a person’s performance.

Assignee Type

Developer identifier: projects.assigneeTypeAssignee Type states default assignee type for the project. It preserves the provider’s current classification of this record.

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

Avatar URLs

Developer identifier: projects.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 jira data center project record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each jira data center project record. Availability still follows the provider’s permissions and retention.

16x16

Developer identifier: projects.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 jira avatar url record.
Interpretation: The provider supplies 16x16 as a URL or resource locator on each jira avatar url record. Availability still follows the provider’s permissions and retention.

24x24

Developer identifier: projects.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 jira avatar url record.
Interpretation: The provider supplies 24x24 as a URL or resource locator on each jira avatar url record. Availability still follows the provider’s permissions and retention.

32x32

Developer identifier: projects.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 jira avatar url record.
Interpretation: The provider supplies 32x32 as a URL or resource locator on each jira avatar url record. Availability still follows the provider’s permissions and retention.

48x48

Developer identifier: projects.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 jira avatar url record.
Interpretation: The provider supplies 48x48 as a URL or resource locator on each jira avatar url record. Availability still follows the provider’s permissions and retention.

Components

Developer identifier: projects.componentsComponents records list of components defined in this project. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Assignee

Developer identifier: projects.components.assigneeAssignee records default assignee for the component. It keeps the provider-reported person or account context attached to the record.

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

Active

Developer identifier: projects.components.assignee.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 jira user record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: projects.components.assignee.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 jira user record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each jira user record. Availability still follows the provider’s permissions and retention.

Display Name

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

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

Email Address

Developer identifier: projects.components.assignee.emailAddressEmail Address records email address of the user. It keeps the provider-reported person or account context attached to the record.

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

Key

Developer identifier: projects.components.assignee.keyKey is the unique key identifying the user (often the username in Data Center). It is needed to resolve references that repeat the same provider identifier.

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

Locale

Developer identifier: projects.components.assignee.localeLocale records locale preference of the user. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

Name

Developer identifier: projects.components.assignee.nameName records username of the user. It keeps the provider-reported person or account context attached to the record.

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

Self

Developer identifier: projects.components.assignee.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 user record.
Interpretation: The provider supplies self as a URL or resource locator on each jira user record. Availability still follows the provider’s permissions and retention.

Time Zone

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

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

Assignee Type

Developer identifier: projects.components.assigneeTypeAssignee Type states default assignee type for the component. It preserves the provider’s current classification of this record.

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

Description

Developer identifier: projects.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 jira component record.
Interpretation: The provider supplies description at jira component granularity in the format stated by its description; omitted or redacted content remains unknown.

Developer identifier: projects.components.idID is the unique numeric ID of the component. It is the key of this nested record.

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

Is Assignee Type Valid

Developer identifier: projects.components.isAssigneeTypeValidIs Assignee Type Valid indicates whether the configured assignee type is valid. It preserves the provider-reported yes-or-no condition for this record.

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

Lead

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

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

Name

Developer identifier: projects.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 jira component record.
Interpretation: The provider supplies name at jira component granularity in the format stated by its description; omitted or redacted content remains unknown.

Project

Developer identifier: projects.components.projectProject records project key this component belongs to. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Project ID

Developer identifier: projects.components.projectIdProject ID reports the numeric ID of the project this component belongs to. It is needed to resolve references that repeat the same provider identifier.

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

Real Assignee

Developer identifier: projects.components.realAssigneeReal Assignee records actual resolved assignee after applying project defaults. It keeps the provider-reported person or account context attached to the record.

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

Real Assignee Type

Developer identifier: projects.components.realAssigneeTypeReal Assignee Type states actual resolved assignee type after applying project defaults. It preserves the provider’s current classification of this record.

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

Self

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

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

Description

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

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

Developer identifier: projects.emailEmail records email address associated with the project, if configured. It keeps the provider-reported person or account context attached to the record.

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

Entity ID

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

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

Expand

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

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

Developer identifier: projects.idID is the unique numeric ID of the project. It is needed to resolve references that repeat the same provider identifier.

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

Is Private

Developer identifier: projects.isPrivateIs Private indicates whether Jira reports the project as private. It documents the access-related value reported for this object.

Enables: describe the provider-reported is private attached to each jira data center project record.
Interpretation: The Jira Data Center REST reference does not define the value, and it does not list who can browse the project. Source permissions read the project’s Browse Projects grants from project_browse_grants, project_role_actors and project_role_users instead.

Issue Types

Developer identifier: projects.issueTypesIssue Types records list of issue types available in this project. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

Avatar ID

Developer identifier: projects.issueTypes.avatarIdAvatar ID is the ID of the avatar associated with this issue type. It is needed to resolve references that repeat the same provider identifier.

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

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 jira issue type record.
Interpretation: The provider supplies description at jira issue type granularity in the format stated by its description; omitted or redacted content remains unknown.

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 jira issue type record.
Interpretation: The provider supplies iconUrl as a URL or resource locator on each jira issue type record. Availability still follows the provider’s permissions and retention.

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

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

Name

Developer identifier: projects.issueTypes.nameName states name of the issue type (e.g., Bug, Story, Task). It preserves the provider’s current classification of this record.

Enables: filter and group project records by the Jira Data Center jira issue type name exposed by the nested object.
Interpretation: The provider supplies name per jira issue type record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 resource. It retains the exact provider location for the referenced resource.

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

Subtask

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

Enables: select project records for which the provider reports subtask as true or false.
Interpretation: The provider supplies subtask as a boolean per jira issue type record; false and missing are distinct when the field is optional. In Jira Data Center, subtask is a condition on the work record, not 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 data center project record across syncs.
Interpretation: The provider supplies key at one value per jira data center project record, and it is the record key.

Lead

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

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

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 data center project record.
Interpretation: The provider supplies name at jira data center project granularity in the format stated by its description; omitted or redacted content remains unknown.

Project Category

Developer identifier: projects.projectCategoryProject Category states administrative category grouping for the project. It preserves the provider’s current classification of this record.

Enables: separate project records by the exact provider-reported project category value when describing their recorded state.
Interpretation: The provider supplies projectCategory per jira data center project record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 jira project category record.
Interpretation: The provider supplies description at jira project category granularity in the format stated by its description; omitted or redacted content remains unknown.

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

Enables: match project records to provider records that carry the same ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies id as a record-level identifier. 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 Data Center jira project category name exposed by the nested object.
Interpretation: The provider supplies name per jira project category record using its own state vocabulary; unknown and missing values must remain distinct. In Jira Data Center, 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 jira project category record.
Interpretation: The provider supplies self as a URL or resource locator on each jira project category record. Availability still follows the provider’s permissions and retention.

Project Keys

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

Enables: enumerate the nested project keys records contained by each jira data center project record.
Interpretation: The provider returns projectKeys as a list; 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, business, service_desk). It is needed to resolve references that repeat the same provider identifier.

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

Properties

Developer identifier: projects.propertiesProperties records arbitrary project properties as key-value pairs. 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.

Roles

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

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

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 data center project record.
Interpretation: The provider supplies self as a URL or resource locator on each jira data center project record. Availability still follows the provider’s permissions and retention.

Simplified

Developer identifier: projects.simplifiedSimplified indicates whether this project uses the simplified project experience. It preserves the provider-reported yes-or-no condition for this record.

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

Style

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

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

URL

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

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

UUID

Developer identifier: projects.uuidUUID identifies UUID of the project if available. It is needed to resolve references that repeat the same provider identifier.

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

Versions

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

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

Archived

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

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

Description

Developer identifier: projects.versions.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 jira version record.
Interpretation: The provider supplies description at jira version granularity in the format stated by its description; omitted or redacted content remains unknown.

Developer identifier: projects.versions.idID is the unique numeric ID of the version. It is the key of this nested record.

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

Name

Developer identifier: projects.versions.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 jira version record.
Interpretation: The provider supplies name at jira version granularity in the format stated by its description; omitted or redacted content remains unknown.

Overdue

Developer identifier: projects.versions.overdueOverdue indicates whether this version is past its release date without being released. It preserves the provider-reported yes-or-no condition for this record.

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

Project ID

Developer identifier: projects.versions.projectIdProject ID reports the numeric ID of the project this version belongs to. It is needed to resolve references that repeat the same provider identifier.

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

Released

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

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

Release Date

Developer identifier: projects.versions.releaseDateRelease Date records planned or actual release date of the version. It anchors the named event or boundary on the record’s timeline.

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

Self

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

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

Start Date

Developer identifier: projects.versions.startDateStart Date records planned start date of the version. It anchors the named event or boundary on the record’s timeline.

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

User Release Date

Developer identifier: projects.versions.userReleaseDateUser Release Date records user-formatted release date string. It anchors the named event or boundary on the record’s timeline.

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

User Start Date

Developer identifier: projects.versions.userStartDateUser Start Date records user-formatted start date string. It anchors the named event or boundary on the record’s timeline.

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

Users

Developer identifier: usersUsers contain Jira Data Center users.

Enables: resolve self-hosted Jira identities referenced by issue records, and supply the user principals that source permissions match Browse Projects grants, group members and project role actors against.
Scope: Reads every record from GET /rest/api/2/user/search on each sync, active and inactive users included. A later complete read treats a previously seen user that is absent as removed, because Jira drops a deleted user from the search. Results contain only Jira records visible to the configured account; permission-hidden projects, issues, and comments are absent.

Active

Developer identifier: users.activeActive indicates whether the user account is active. Filters active vs deactivated users for license and adoption analysis. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports active as true or false.
Interpretation: The provider supplies active as a boolean per jira data center user record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not a measure of a person’s performance. For source permissions, Parable marks a user whose value is false, null or absent as inactive, so that user reads no Jira Data Center row.

Application Roles

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

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

Items

Developer identifier: users.applicationRoles.itemsItems states array of application role objects. It documents the access-related value reported for this object or membership.

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

Key

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

Enables: match user records to provider records that carry the same key, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies key as a record-level identifier. 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 record.
Interpretation: The provider supplies name at application role granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Data Center, name describes access or membership, not a person’s performance.

Self

Developer identifier: users.applicationRoles.items.selfSelf captures the URL of the application role’s REST API resource. It retains the exact provider location for the referenced resource.

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

Size

Developer identifier: users.applicationRoles.sizeSize reports the number of application roles returned in the list. It records collection occupancy for the response.

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

Avatar URLs

Developer identifier: users.avatarUrlsAvatar URLs records map of avatar image URLs at various sizes. It retains the exact provider location for the referenced resource.

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

16x16

Developer identifier: users.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: users.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: users.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: users.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. Parable uses this image as the person’s photo.

Deleted

Developer identifier: users.deletedDeleted indicates whether Jira reports the user account as deleted. It preserves the provider-reported yes-or-no condition for this record.

Enables: select user records for which the provider reports deleted as true or false.
Interpretation: Jira drops a deleted user from user/search, so the tap treats an absent user as removed. This field does not mark rows deleted.

Display Name

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

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

Email Address

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

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

Expand

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

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

Groups

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

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

Items

Developer identifier: users.groups.itemsItems records array of group objects. It preserves the containing or referenced object needed to reconstruct the provider relationship.

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

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 record.
Interpretation: The provider supplies name at group granularity in the format stated by its description; omitted or redacted content remains unknown.

Self

Developer identifier: users.groups.items.selfSelf captures the URL of the group’s REST API resource. It retains the exact provider location for the referenced resource.

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

Size

Developer identifier: users.groups.sizeSize reports the number of groups returned in the list. It records collection occupancy for the response.

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

Key

Developer identifier: users.keyKey is the unique user key in Jira Data Center. Primary key for joining users to issues, worklogs, and changelogs. It is the record key, so rows with the same value describe the same record.

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

Locale

Developer identifier: users.localeLocale records user’s configured locale (e.g., en_US). It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

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

Name

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

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

Self

Developer identifier: users.selfSelf captures the URL of the user’s REST API resource. It retains the exact provider location for the referenced resource.

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

Time Zone

Developer identifier: users.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 users using the recorded time zone.
Interpretation: The provider supplies timeZone as location or localization context per jira data center user record; it does not establish a person’s real-time physical location.

Worklogs

Developer identifier: worklogsWorklogs contain the work logged against Jira Data Center issues, with author, time spent and visibility.

Enables: inspect logged work per issue with author, start time, duration and visibility context, without treating logged time as individual performance.
Scope: Reads every record from GET /rest/api/2/issue/{id}/worklog for each issue that the issues sync reads: one request per changed issue, so the tap is off by default. Jira returns no worklog when the Log work field is hidden for the project. The issue keeps its time totals (timespent, aggregatetimespent, timetracking) without this tap. has_visibility is true when the worklog is restricted to a group or a project role.

Author

Developer identifier: worklogs.authorAuthor records user who logged the work. It keeps the provider-reported person or account context attached to the record.

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

Account ID

Developer identifier: worklogs.author.accountIdAccount ID is the unique account ID (Atlassian account ID, if applicable). It is needed to resolve references that repeat the same provider identifier.

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

Active

Developer identifier: worklogs.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 record; false and missing are distinct when the field is optional. In Jira Data Center, active is a condition on the work record, not a measure of a person’s performance.

Avatar URLs

Developer identifier: worklogs.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 record.
Interpretation: The provider supplies avatarUrls as a URL or resource locator on each user record. Availability still follows the provider’s permissions and retention.

16x16

Developer identifier: worklogs.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: worklogs.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: worklogs.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: worklogs.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: worklogs.author.displayNameDisplay Name records full display name of the user. It keeps the provider-reported person or account context attached to the record.

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

Email Address

Developer identifier: worklogs.author.emailAddressEmail Address records email address of the user. It keeps the provider-reported person or account context attached to the record.

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

Key

Developer identifier: worklogs.author.keyKey identifies user key (unique identifier in Jira Data Center). It is needed to resolve references that repeat the same provider identifier.

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

Name

Developer identifier: worklogs.author.nameName records username / login name. It keeps the exact text, label, or authored value needed to interpret the record.

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

Self

Developer identifier: worklogs.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 record.
Interpretation: The provider supplies self as a URL or resource locator on each user record. Availability still follows the provider’s permissions and retention.

Time Zone

Developer identifier: worklogs.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 record; it does not establish a person’s real-time physical location.

Comment

Developer identifier: worklogs.commentComment records comment on the worklog entry. It keeps the exact text, label, or authored value needed to interpret the record.

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

Created

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

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

Has Visibility

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

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

Developer identifier: worklogs.idID is the unique ID of the worklog. It is the record key, so rows with the same value describe the same record.

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

Issue ID

Developer identifier: worklogs.issue_idIssue ID identifies the parent issue. Parable copies its ID from the parent record in issues. Absent from the Jira worklog API response body itself.

Enables: match worklog records to the issue they belong to.
Interpretation: For source permissions, a worklog inherits the readers of this issue unless it has a visibility.

Issue Key

Developer identifier: worklogs.issue_keyIssue Key identifies the key of the parent issue (e.g. PROJ-42). Parable copies it from the parent record in issues.

Enables: show which issue a worklog belongs to.
Interpretation: An issue that moves to another project gets a new key, so match on issue_id.

Self

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

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

Started

Developer identifier: worklogs.startedStarted records the timestamp when the work was started. It anchors the named event or boundary on the record’s timeline.

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

Time Spent

Developer identifier: worklogs.timeSpentTime Spent reports human-readable time spent (e.g., 3h 20m). It preserves the elapsed interval reported for this record.

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

Time Spent Seconds

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

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

Update Author

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

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

Updated

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

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

Visibility

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

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

Type

Developer identifier: worklogs.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 record.
Interpretation: The provider supplies type at visibility granularity. It describes provider-reported context and does not prove effective access beyond the returned record. In Jira Data Center, type describes access or membership, not a person’s performance.

Value

Developer identifier: worklogs.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.

Error	Meaning	Solution
`401 Unauthorized`	Invalid credentials	Verify username and token/password
`403 Forbidden`	No permission	Check user has required permissions
`403` on `/permissionscheme` or `/role/{id}`	The token’s account is not a Jira administrator	Create the token as an account with the Jira Administrators global permission
`Connection refused`	Network issue	Verify server URL and network access

Common Issues

PATs not available

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

SSL certificate errors

Self-signed certificates may cause issues. Ensure proper certificate configuration.Jira Server REST API — Official API documentation

​Data streams

​Personal access token

​What You’ll Need

​Step 1: Access Profile Settings

​Step 2: Create Personal Access Token

​Step 3: Note Your Base URL

​Step 4: Enter values in the form

​Who reads Jira Data Center rows

​Common Issues

​PATs not available

​SSL certificate errors

Data streams

Personal access token

What You’ll Need

Step 1: Access Profile Settings

Step 2: Create Personal Access Token

Step 3: Note Your Base URL

Step 4: Enter values in the form

Who reads Jira Data Center rows

Common Issues

PATs not available

SSL certificate errors