![]() |
VOOZH | about |
You can use the SQL Gateway from the ODBC Driver for Jira Assets to query Jira Assets data through a MySQL interface. Follow the procedure below to start the MySQL remoting service of the SQL Gateway and work with live Jira Assets data in MySQL Workbench.
If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.
Jira Assets supports connecting and authenticating via the APIToken.
To generate an API token:
Atlassian generates and then displays the API token.
After you have generated the API token, set these parameters:
You are now ready to connect and authenticate to Jira Assets.
See the SQL Gateway Overview to set up connectivity to Jira Assets data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.
👁 Creating a MySQL Remoting Service in SQL Gateway (Salesforce is shown)
The steps below outline connecting to the virtual Jira Assets database created in the SQL Gateway from MySQL Workbench and issuing basic queries to work with live Jira Assets data.
NOTE: When we refer to Username and Password, we mean the credentials for the user(s) created for the SQL Gateway.
👁 ImageWith access to live Jira Assets data from MySQL Workbench, you can easily work with Jira Assets, just like you would a MySQL database. Get started now with a free, 30-day trial of the CData ODBC Driver for Jira Assets and the CData SQL Gateway.
Download a free trial of the Jira Assets ODBC Driver to get started:
Download NowLearn more:
👁 Jira Assets IconThe Jira Assets ODBC Driver is a powerful tool that allows you to connect with live data from Jira Assets, directly from any applications that support ODBC connectivity.
Access Jira Assets data like you would a database - read, write, and update Jira Assets 0, etc. through a standard ODBC Driver interface.