Devart ODBC Driver for Jira: Jira Issues and Projects in Excel, Power BI and SQL
Devart ODBC Driver for Jira is a Windows ODBC driver that gives Excel, Power BI, Tableau, Access, SQL Server and scripts SQL access to Jira data, including your custom fields. It works with Jira Cloud (API token or OAuth sign-in) and with self-hosted Jira servers (user name and password), and costs $109.95 a year for one Windows desktop.
Jira is where the work is tracked, but the questions about that work (how long bugs stay open, how much each team shipped, which customer requests are stuck) are usually answered in a spreadsheet or a BI dashboard. The driver is the bridge: Jira becomes tables those tools can refresh, without exporting CSVs or writing REST API code.
Quick facts
- Version: 2.3.0, released October 16, 2026; the driver first came out in November 2022
- Developer: Devart
- Operating systems: Windows Vista or later, 32-bit and 64-bit, including Terminal Server; .NET Framework 4.5
- Jira versions: Jira Cloud and self-hosted ("local server") Jira, with a selectable API version
- Authentication: Atlassian API token with your user ID, OAuth sign-in to a Jira Cloud site, or user name and password for a local server
- SQL: SELECT with joins, subqueries, grouping and aggregates; INSERT, UPDATE and DELETE; custom tables and fields
- Price: $109.95 a year, or $219.95 perpetual, for Desktop for Windows
- Trial: 30 days, full-featured
- Refunds: under Devart's ordering FAQ, a full refund within 30 days only if a technical problem or bug that Devart support can't fix stops the driver working
- What we checked: the order page priced ODBC Driver for Jira at $109.95 for the default Desktop for Windows edition on a 1-year subscription renewing yearly, and the download page listed version 2.3.0 with a 34.06 MB EXE and a 38.22 MB MSI, both on November 15, 2026. We didn't connect it to a Jira site
Before you buy
The driver sees what the account you connect with can see in Jira. If you sign in with your own API token, a report built on it shows only the projects and issues you have permission to browse; for team-wide dashboards, connect with an account that has access to every project you report on. Jira Service Management has its own separate Devart driver, so buy that one if service-desk queues and requests are what you need.
Download Free TrialBuy Now
Overview
Devart released the Jira driver in November 2022 and moved it to version 2 in April 2025, when it added metadata caching and what Devart calls a significant speed-up in reading data. The release that matters most for real Jira sites came earlier, in October 2023: support for custom tables and custom fields. Almost every Jira site has custom fields (story points, customer, team, severity), and a driver that can't see them is of little use for reporting.
Recent releases have been about fitting into more tools: Microsoft Query and Excel imports, Tableau, Qlik Replicate, Vectorworks, PHP's PDO_ODBC, Node.js, DBeaver and Visual FoxPro. Devart publishes setup guides for 47 tools that use the Jira driver, from Excel and Power BI to MATLAB, Informatica, Denodo and FileMaker.
Features
Three ways to sign in
Devart ODBC Driver for Jira connects to Jira Cloud either with your Atlassian account's user ID and an API token you create under Security in your account settings, or through an OAuth sign-in that fills in the cloud site name, cloud ID and a refresh token for you. For a Jira server you run yourself, choose the local-server environment and enter the domain, user name and password. Since version 1.3.0 tokens and passwords are stored encrypted in the DSN.
Your custom fields as columns
Devart ODBC Driver for Jira exposes custom tables and custom fields, and a Custom Objects option controls whether user-defined objects are used in imports, exports and synchronization. That's what lets a report group issues by your own "Team" field or sum your "Story Points".
SQL reads and writes
Devart ODBC Driver for Jira runs SQL-92 SELECT statements with joins, WHERE filters, subqueries, GROUP BY, aggregates and ORDER BY, and supports INSERT, UPDATE and DELETE, so a script or an Access form can change Jira data as well as read it.
Faster table lists with metadata caching
Devart ODBC Driver for Jira 2.0 added a Cache Metadata setting that keeps the list of tables and columns for a period you choose, so BI tools that re-read the schema on every refresh don't wait on Jira each time. Foreign-key metadata is off by default for the same reason.
Benefits
- Reports outside Jira's own gadgets. Build the cycle-time chart or the cross-project burn-up your team actually wants, in the tool you already use.
- Jira next to other data. Join issues to time-tracking, billing or CRM data in Power BI or a SQL Server linked server.
- No API code. Analysts get Jira data without anyone writing and maintaining REST calls.
- Cloud and server alike. The same driver and the same SQL work if you're still on a self-hosted Jira or have moved to Cloud.
Real-World Uses
- An engineering manager refreshes an Excel workbook every Monday showing open bugs by priority and age for each team.
- A PMO builds a Power BI portfolio report across dozens of Jira projects, grouped by a custom "Initiative" field.
- A finance analyst joins Jira issues to billable hours from the accounting database to see which client projects overran.
- A DBA adds a SQL Server linked server to Jira so a nightly job copies issues into a data warehouse.
- A company moving from Jira Server to Cloud runs the same queries against both to check the migration.
Who It's For, and Who Should Skip It
It's for Windows-based analysts, project managers, PMOs and data teams who report on Jira in Excel, Power BI, Tableau, Access or SQL Server, especially across many projects or with custom fields.
Skip it if Jira's built-in dashboards and filters already answer your questions, or if you only need an occasional CSV export. If you need Jira data in a cloud data warehouse on a schedule, an ETL service may suit you better than a desktop driver. And Mac or Linux users can't run it.
Usage Guide
- For Jira Cloud with a token: in your Atlassian account settings, go to Security, open "Create and manage API tokens", create one and copy it right away.
- Run the driver's EXE (or MSI for managed rollouts) and choose Trial evaluation or enter your key.
- Open the ODBC Data Source Administrator that matches your application's bitness (32-bit or 64-bit) and add a DSN for Devart ODBC Driver for Jira.
- Pick the environment and authentication: domain, user ID and API token; Sign in for OAuth; or domain, user and password for a local server.
- Click Test Connection and save.
- Choose the DSN in your tool, for example Excel's Get Data > From ODBC or Power BI's ODBC connector, then pick the tables you need.
Where it falls short
- Every query becomes Jira API calls, so large sites and wide date ranges are slower than a database, and Atlassian's limits on API traffic apply.
- An API token is shown only once when you create it; lose it and you create a new one and update the DSN.
- Only one version of the driver can be installed on a PC at a time.
- A DSN made in the wrong-bitness ODBC administrator won't show up in your application, the usual cause of "data source not found".
- There are no macOS or Linux builds.
What Users Say
Reviews of the Devart ODBC family
The Jira driver hasn't collected reviews of its own; Capterra lists Devart's ODBC drivers together, at 4.7 out of 5 across 26 reviews. Those reviewers mainly use the database and Salesforce drivers. They value the quick install and steady connections, and the most common criticism is cost. Jira teams should test their own custom fields and largest projects in the 30-day trial before relying on those general marks.
Comparisons
ODBC Driver for Jira vs ODBC Driver for Jira Service Management
Devart sells these as two drivers. The Jira driver is for Jira software projects; the Jira Service Management driver is for service-desk data. If you need both, Devart's ODBC Universal Bundle includes both along with every other Devart ODBC driver.
ODBC driver vs exporting from Jira
Jira can export search results to CSV or Excel for free, but each export is a snapshot you redo by hand. The driver gives a live connection that refreshes, joins with other data and can write changes back, which pays off once a report is run every week.
Editions and Pricing
Use the one Buy Now button for any edition: the order page starts on Desktop for Windows with a 1-year subscription, and the edition, license type (subscription or perpetual) and term are chosen there.
| Edition | 1-year subscription | Perpetual | Typical use |
| Desktop for Windows | $109.95 | $219.95 | An analyst's own PC |
| Server Standard for Windows | $799.95 | $1,599.95 | A reporting or SQL Server box (up to 6 cores) shared by many users |
| Server Enterprise, Site, OEM | Quote | Quote | Larger servers, company-wide installs, or shipping the driver in your product |
FAQs
Does Devart ODBC Driver for Jira work with Jira Data Center or Server?
Yes. Devart ODBC Driver for Jira has a local-server environment for self-hosted Jira, where you connect with the server's domain and a Jira user name and password instead of an Atlassian API token.
Can I connect Power BI to Jira with this driver?
Yes. Devart ODBC Driver for Jira appears as an ODBC data source in Power BI Desktop; pick its DSN in Get Data > ODBC and choose the tables to load, or type a SQL statement to load only what you need.
Should I use an API token or OAuth?
Both work with Jira Cloud. Devart ODBC Driver for Jira's API-token method is simple for one person's DSN; the OAuth method signs you in through Atlassian and stores a refresh token, so no token has to be copied by hand.
Can several people share one Jira driver license?
Not a Desktop license, which allows one computer used by one person at a time. For a shared reporting server or simultaneous users, Devart ODBC Driver for Jira needs a Server Standard or Server Enterprise license.
Can I deploy the Jira driver to many PCs silently?
Yes. Devart ODBC Driver for Jira comes as an MSI that can be installed through Group Policy, and it also supports silent installation from the command line.
System Requirements
- Windows Vista or later, 32-bit or 64-bit, including Windows Terminal Server
- .NET Framework 4.5 or later
- Only one version of the driver installed on the computer
- A Jira Cloud site with an API token or OAuth sign-in, or a self-hosted Jira server with a user account
Conclusion
For $109.95 a year, Devart's Jira driver is a sensible buy if you report on Jira every week in Excel, Power BI or SQL Server: custom-field support, both Cloud and self-hosted connections, and write-back make it more than an export tool. The reason to hold off is scale and platform: very large Jira sites pay for every query in API calls, and it's Windows-only, so try it on your biggest project during the trial.
Download Free TrialBuy Now