Jira is an issue tracking solution with bug tracking, issue tracking, and project management functions.
Data integration: Skyvia supports importing data to and from Jira, exporting Jira data to CSV files, replicating Jira data to relational databases, and synchronizing Jira data with other cloud apps and relational databases.
Backup: Skyvia Backup supports Jira backup.
Query: Skyvia Query supports Jira.
Jira-Specific Features and Limitations
Skyvia has the following limitations for Jira:
|•||Synchronization and Replication with Incremental Updates enabled are not supported for objects without CreateDate and UpdatedDate fields. Both fields must be present for this functionality. Thus, only the Issues object supports Synchronization and Replication with Incremental Updates.|
|•||Skyvia does not support custom fields in the default Jira connector. However, if you need to work with custom fields in Jira, you may contact our support team.|
|•||Some of the Jira objects can be accessed only via their parent objects. For example, to query ProjectComponents, ProjectStatuses, ProjectProperties, and ProjectVersions objects, Jira API requires the id of the corresponding project. To get IssueComments, RemoteIssueLinks, IssueTransitions, IssueVotes, or IssueWorklogs records, Jira API requires the id of the corresponding issue.|
Skyvia does not require this id of the parent object from user. If you don't specify the ids of the parent objects (for example, in a filter), Skyvia queries all the parent object records first, takes their ids, and then queries child object records for each parent object record. This allows querying child objects without knowing their parents, but this method takes much time and consumes many API calls. It uses at least one API call for every parent object record (for example, Issue), even if this record does not have actually any queried child records (for example, IssueComments). This means that even if there is only a small number of IssueComments in your Jira, querying them still may take much time and API calls if there are a lot of issues.
Thus, it is strongly recommended to use filters on the parent object fields when querying data from such child objects. This limits the number of parent object records, for which child object data must be queried.
To connect to Jira, you need to specify the domain to connect to and the user email and password to login.
You need to specify the following parameters for a Jira connection:
|•||Name - connection name that will be used to identify the connection on the Connections page and when selecting a connection for a package.|
|•||Domain - the domain where Jira is running.|
|•||User - the user email to login with.|
|•||Password - the password to your Jira account.|