skip to main content
Welcome to the Progress DataDirect for JDBC for Jira Driver: Version 6.0.0 : Introduction to the Jira Data Model
  

Try DataDirect Drivers Now

Introduction to the Jira Data Model

To expose Jira resources to SQL applications, the driver maps the native data model to relational tables and translates SQL statements to REST API requests. See "Mapping Objects to Tables" for more information on relational mapping.
Although the JIRA environment promotes customization, a similar set of resources are used by most Jira services. The following table documents the types of Jira API Resources you are likely to encounter in your environment, along with the relational mapping of the primary and child tables. Refer to the Jira documentation for more information on resources.
Table 1. Jira API Resource Mapping
Jira API Resource
Relational Parent Table(s)
Relational Child Table(s)
Application roles
ApplicationRoles
*ApplicationRolesDefaultGroups
*ApplicationRolesGroups
Audit records
Auditing
*AuditingAssociatedItems
*AuditingChangedValues
Dashboards
Dashboards
DashboardSharePermissions
Filters
Filters
*FilterSharedUserItems
*FilterSharePermissions
*FilterSubscriptions
FilterDefaultColumns
NA
Groups
Groups
GroupLabels
GroupUsers
NA
Issue attachment
Attachments
NA
AttachmentMeta
NA
Issue comment properties
CommentProperty
NA
CommentPropertyKeys
NA
Issue comments
Comments
NA
Issue fields
Fields
FieldClauseNames
Issue link types
IssueLinkTypes
NA
Issue resolutions
Resolutions
NA
Issue types
IssueTypes
NA
Issue votes
Votes
Voters
Issue watchers
Watchers
NA
Issue worklogs
Worklogs
*WorklogProperties
*WorklogPropertyValues
Issues
Issues
*IssueAttachments
*IssueComments
*IssueComponents
*IssueFixVersions
*IssueLabels
*IssueLinks
*IssueSubtasks
*IssueVersions
*IssueWorklogs
IssueChangeLog
NA
IssueChangeLogItems
NA
IssueTransitions
NA
Comments:
*Primary table contains a record of all the Issues. Note that issuing unfiltered queries against large data sources may take a long time to process. To limit the number of rows returned, use the following statements:
SELECT TOP
or
SELECT ... LIMIT
*The IssueChangeLog tables require either an ID or a KEY, in the Where clause.
Jira expressions
Boards
NA
Epics
NA
Sprints
NA
Comments:The Sprints table requires either an ID or a KEY, in the Where clause.
Jira settings
AdvancedSettings
AdvancedSettingsAllowedValues
ApplicationProperties
ApplicationPropertiesAllowedValues
Configuration
NA
Permissions
MyPermissions
NA
Projects
Projects
ProjectIssueTypes
Project components
Components
NA
Project Versions
ProjectVersions
ProjectKey
Project role actors
Roles
RoleActors
Users
UserDetails
*UserApplicationRoles
*UserGroups
*Users
Workflows
Workflows
NA