Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Build Jira-Connected ETL Processes in Google Data Fusion
Load the CData JDBC Driver into Google Data Fusion and create ETL processes with access live Jira data.
Google Data Fusion allows users to perform self-service data integration to consolidate disparate data. Uploading the CData JDBC Driver for Jira enables users to access live Jira data from within their Google Data Fusion pipelines. While the CData JDBC Driver enables piping Jira data to any data source natively supported in Google Data Fusion, this article walks through piping data from Jira to Google BigQuery,
About Jira Data Integration
CData simplifies access and integration of live Jira data. Our customers leverage CData connectivity to:
- Gain bi-directional access to their Jira objects like issues, projects, and workflows.
- Use SQL stored procedures to perform functional actions like changing issues status, creating custom fields, download or uploading an attachment, modifying or retrieving time tracking settings, and more.
- Authenticate securely using a variety of methods, including username and password, OAuth, personal access token, API token, Crowd or OKTA SSO, LDAP, and more.
Most users leverage CData solutions to integrate Jira data with their database or data warehouse, whether that's using CData Sync directly or relying on CData's compatibility with platforms like SSIS or Azure Data Factory. Others are looking to get analytics and reporting on live Jira data from preferred analytics tools like Tableau and Power BI.
Learn more about how customers are seamlessly connecting to their Jira data to solve business problems from our blog: Drivers in Focus: Collaboration Tools.
Getting Started
Upload the CData JDBC Driver for Jira to Google Data Fusion
Upload the CData JDBC Driver for Jira to your Google Data Fusion instance to work with live Jira data. Due to the naming restrictions for JDBC drivers in Google Data Fusion, create a copy or rename the JAR file to match the following format driver-version.jar. For example: cdatajira-2020.jar
- Open your Google Data Fusion instance
- Click the to add an entity and upload a driver
- On the "Upload driver" tab, drag or browse to the renamed JAR file.
- On the "Driver configuration" tab:
- Name: Create a name for the driver (cdata.jdbc.jira) and make note of the name
- Class name: Set the JDBC class name: (cdata.jdbc.jira.JIRADriver)
- Click "Finish"
Connect to Jira Data in Google Data Fusion
With the JDBC Driver uploaded, you are ready to work with live Jira data in Google Data Fusion Pipelines.
- Navigate to the Pipeline Studio to create a new Pipeline
- From the "Source" options, click "Database" to add a source for the JDBC Driver
- Click "Properties" on the Database source to edit the properties
NOTE: To use the JDBC Driver in Google Data Fusion, you will need a license (full or trial) and a Runtime Key (RTK). For more information on obtaining this license (or a trial), contact our sales team.
- Set the Label
- Set Reference Name to a value for any future references (i.e.: cdata-jira)
- Set Plugin Type to "jdbc"
- Set Connection String to the JDBC URL for Jira. For example:
jdbc:jira:RTK=5246...;User=admin;Password=123abc;Url=https://yoursitename.atlassian.net;To connect to JIRA, provide the User and Password. Additionally, provide the Url; for example, https://yoursitename.atlassian.net.
Built-in Connection String Designer
For assistance in constructing the JDBC URL, use the connection string designer built into the Jira JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.
java -jar cdata.jdbc.jira.jar
Fill in the connection properties and copy the connection string to the clipboard.
- Set Import Query to a SQL query that will extract the data you want from Jira, i.e.:
SELECT * FROM Issues
- From the "Sink" tab, click to add a destination sink (we use Google BigQuery in this example)
- Click "Properties" on the BigQuery sink to edit the properties
- Set the Label
- Set Reference Name to a value like jira-bigquery
- Set Project ID to a specific Google BigQuery Project ID (or leave as the default, "auto-detect")
- Set Dataset to a specific Google BigQuery dataset
- Set Table to the name of the table you wish to insert Jira data into
With the Source and Sink configured, you are ready to pipe Jira data into Google BigQuery. Save and deploy the pipeline. When you run the pipeline, Google Data Fusion will request live data from Jira and import it into Google BigQuery.
While this is a simple pipeline, you can create more complex Jira pipelines with transforms, analytics, conditions, and more. Download a free, 30-day trial of the CData JDBC Driver for Jira and start working with your live Jira data in Google Data Fusion today.