Jira
DLH.io documentation for Jira
Jira Software is part of a family of products designed to help teams of all types manage work. Originally, Jira was designed as a bug and issue tracker. But today, Jira has evolved into a powerful work management tool for all kinds of use cases, from requirements and test case management to agile software development. DLH.io connects to Jira Cloud using OAuth 2.0 with read only access. Jira Server and Data Center connections are not yet supported.
Setup Instructions
Follow the setup steps guide for configuring your Jira connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Issues and their links, comments, worklogs and history are read by last updated date |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | ||
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
- Reference data (statuses, priorities, issue types, fields, projects, users and similar) is read in full on every run.
- Issues are read per project. The first synchronization, or a historical re-sync, reads every issue in each project regardless of the Historical Start Date. Later runs read issues updated since the previous run, less a lookback margin. Issue links, comments, worklogs and field history are read together with their issues.
- Field history: change history is captured for custom fields only.
ISSUE_FIELD_HISTORYholds changes to single value custom fields andISSUE_MULTISELECT_HISTORYholds one row per option for multi select custom fields. - Requests are paced (a small number run in parallel) and rate limited responses are retried.
- Authorization and scope: DLH.io connects with OAuth 2.0 and every scope requested is read only: this connector never creates, updates or deletes anything in your Jira instance. DLH.io does not capture or store your Atlassian password.
- Jira Server and Data Center connections are not yet supported.
Issue Handling
If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Authorize Your Account button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.
Replicated Entities
The following entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:
Reference data
Read in full on every run.
PERMISSION_SCHEMEPROJECT_CATEGORYRESOLUTIONSECURITY_SCHEMESTATUSSTATUS_CATEGORYPRIORITYISSUE_TYPEFIELDLABELPROJECT_ROLEISSUE_LINK_TYPE
Projects and users
Projects, their versions and components, users, user groups and project role actors.
PROJECTUSERVERSIONCOMPONENTUSER_GROUPPROJECT_ROLE_ACTOR
Issues
Issues and the records read with them.
ISSUEISSUE_LINKCOMMENTWORKLOGISSUE_FIELD_HISTORYISSUE_MULTISELECT_HISTORY
Schema Details (ER Diagram)
This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.