Please enable JavaScript to view this site.

JIRA Cloud Forums

JIRA Cloud API Data Model

Navigation: » No topics above this level «

JIRA Cloud API SQL Driver

Invantive SQL is the fastest, easiest and most reliable way to exchange data with the JIRA Cloud API.

Use the "Search" option in the left menu to search for a specific term such as the table or column description. When you already know the term, please use the "Index" option. When you can't find the information needed, please click on the Chat button at the bottom or place your question in the <link displaytype="text" defaultstyle="true" type="weblink" href="https://forums.invantive.com/">user community</link>. Invantive Support or other users will try to help you.

JIRA is cloud software for managing business processes and sharing knowledge. JIRA Cloud offers tickets and customized workflows.

The JIRA Cloud driver covers 82 tables and 1536 columns.

JIRA Cloud API Clients

Invantive SQL is available on many user interfaces ("clients" in traditional server-client paradigma). All Invantive SQL statements can be exchanged with a close to 100% compatibility across all clients and operating systems (Windows, MacOS, Linux, iOS, Android).

The clients include Microsoft Excel, Microsoft Power BI, Microsoft Power Query, Microsoft Word and Microsoft Outlook. Web-based clients include Invantive Cloud, Invantive Bridge Online as OData proxy, Invantive App Online for interactive apps, Online SQL Editor for query execution and Invantive Data Access Point as extended proxy.

The <link displaytype="text" defaultstyle="true" type="weblink" href="https://cloud.invantive.com/jira" target="_blank" styleclass="Normal" translate="true">JIRA Cloud Power BI connector</link> is based on the Invantive SQL driver for JIRA Cloud, completed by a high-performance OData connector which works straight on Power BI without any add-on. The OData protocol is always version 4, independent whether the backing platform uses OData, SOAP or another protocol.

For technical users there are command-line editions of Invantive Data Hub running on iOS, Android, Windows, MacOS and Linux. Invantive Data Hub is also often used for enterprise server applications such as ETL. High-volume replication of data taken from the JIRA Cloud API into traditional databases such as SQL Server (on-premises and Azure), MySQL, PostgreSQL and Oracle is possible using <link displaytype="text" defaultstyle="true" type="weblink" href="https://data-replicator.cloud/" target="_blank" styleclass="Normal" translate="true">Invantive Data Replicator</link>. Invantive Data Replicator automatically creates and maintains JIRA Cloud datawarehouses, possibly in combination with data from over 75 other (cloud) platforms. Invantive Data Replicator supports data volumes up to over 1 TB and over 5.000 companies. The on-premise edition of Invantive Bridge offers an JIRA Cloud ADO.net provider.

Finally, online web apps can be build for JIRA Cloud using App Online of <link displaytype="text" defaultstyle="true" type="weblink" href="https://cloud.invantive.com/jira" target="_blank" styleclass="Normal" translate="true">Invantive Cloud</link>.

Monitor API Calls

When a query or DML-statement has been executed on Invantive SQL a developer can evaluate the actual calls made to the JIRA Cloud API using a query on sessionios@DataDictionary. As an alternative, extensive request and response logging can be enabled by setting log-native-calls-to-disk to true. In the %USERPROFILE%\Invantive\NativeLog folder Invantive SQL will create log files per JIRA Cloud API request and response.

Specificaties

The SQL driver for JIRA Cloud does not support partitioning. Define one data container in a database for each company in JIRA Cloud to enable parallel access for data from multiple companies.

Een inleiding in de concepten van Invantive SQL zoals databases, data containers en partitionering is te vinden in de <link displaytype="text" defaultstyle="true" type="weblink" href="https://go.invantive.com/sqlgrammar" target="_blank" styleclass="Normal" translate="true">Invantive SQL grammatica</link>.

The configuration can be changed using various attributes during log on and use. A full list of configuration options is listed in the driver attributes.

The catalog name is used to compose the full qualified name of an object like a table or view. The schema name is used to compose the full qualified name of an object like a table or view. On JIRA Cloud the comparison of two texts is case sensitive by default.

Changes and bug fixes on the JIRA Cloud SQL driver can be found in the release notes. There is currently no specific section on the Invantive forums for JIRA Cloud. Please reach out to other users of JIRA Cloud by leaving a question or contact request.

Driver code for use in settings.xml: JIRA

Alias: jiracloud

Aanbevolen alias: jrc

Status: Non-production

More technical documentation as provided by the supplier of the JIRA Cloud API on the native APIconnection used can be found at https://developer.atlassian.com/jiradev/jira-apis/jira-rest-apis.

General documentation on JIRA Cloud is available at https://jira-apps.com

AuthenticationAuthentication can be done using one of the following two alternatives:1. Using the user log on code, token and server name from the JIRA URL (basic authentication).2. Using OAuth code grant flow.Authentication using user log on code and token is recommended for on-premise use. The basic authentication token can be defined on https://id.atlassian.com/manage/api-tokens. The OAuth code grant flow is recommended for online use; register a client at https://developer.atlassian.com/apps.

19-12-2022 16:35 Version 22.1.113-BETA+3734

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer