SSIS Data Flow Components for Jira: Read and Write Jira Issues in SSIS
Devart SSIS Data Flow Components for Jira add a Jira Source, Destination, Lookup and Connection Manager to SQL Server Integration Services on Windows, for $149.95 a year (Developer license) or $299.95 perpetual. They read Jira issues, projects, users and other objects with SQL, write back with inserts, updates and deletes, and connect to Jira Cloud (API token or OAuth) or Jira Server.
Jira holds the record of what a team worked on, but its reports stop at Jira. Getting issues into a SQL Server warehouse for time, cost or delivery reporting usually means writing code against Jira's REST API and handling paging, custom fields and token refresh yourself. Devart's components turn Jira objects into tables an SSIS package can read and write.
Quick facts
- Version: 5.1.49, released August 17, 2026
- Developer: Devart
- Components: Jira Source, Jira Destination, Jira Lookup, Jira Connection Manager
- Jira: Jira Cloud and Jira Server, Jira data types and API, including custom fields and custom objects for issues
- SSIS: SQL Server Integration Services 2012, 2014, 2016, 2017, 2019, 2022 and 2025
- Platform: Windows Vista or later, 32-bit and 64-bit, .NET Framework 4.5
- Download: 618.60 MB installer shared with the whole SSIS line; needs a free Devart account
- Price: $149.95 a year or $299.95 perpetual for a Developer license; Server and Site licenses cost more
- Trial: 30 days, fully functional
- Refund: Devart's ordering FAQ gives a refund within 30 days only when a technical problem that support can't fix stops the product working
- What we checked: the order page charged $149.95 for the Developer license with one year of updates, $299.95 for a perpetual Developer license, $379.95 a year or $749.95 perpetual for Server, and $499.95 a year or $999.95 perpetual for a Site license, and the download page listed version 5.1.49 at 618.60 MB, on November 19, 2026. We didn't run a package against a Jira site
Download Free Trial Buy Now
Overview
After installation the Jira components appear in the SSIS Toolbox in Visual Studio. You add a Devart Jira Connection Manager, choose Cloud or Server, enter your Jira domain and sign in, then drop a Source, Destination or Lookup into a Data Flow task. Jira objects show up as tables: Issues with fields such as Key, Summary, Status_Name, Project_Name and IssueType_Name, plus related objects like IssueRemoteLinks and IssueResolutions. Everything else works like native SSIS, so Jira can sit on either side of a package next to SQL Server, flat files or other sources.

The Devart Jira Source Editor: the Issues table and its fields on the left, a SELECT of Id, Key, Summary, Project_Name and Status_Name filtered by creation date, and the Preview Data window listing issues of a sample project.
Features
SQL over Jira issues and projects
The Jira Source in Devart SSIS Data Flow Components for Jira reads issues, projects, users and other Jira objects with SQL, including grouping, filtering and ordering. Simple statements are translated into Jira API calls and run on the Jira side; for complex ones the data is fetched into a local cache and the query runs there. The editor lists objects and fields, builds a query by drag and drop, inserts package variables and previews the result.
Write changes back to Jira
The Jira Destination in Devart SSIS Data Flow Components for Jira supports INSERT, UPDATE and DELETE, so a package can create or update issues from another system or a CSV file. Its properties name the target object (Issues, for example) and the batch size.
Custom fields that line up across projects
Devart SSIS Data Flow Components for Jira 5.0 (June 2026) added custom objects for issues, more Jira objects, and a merge option for custom fields: when different projects define custom fields with the same name, you choose how they are combined into one column of the Issues table, so a cross-project report doesn't end up with dozens of near-duplicate columns.
Jira Cloud and Jira Server sign-in
The Devart Jira Connection Manager in SSIS Data Flow Components for Jira connects to Jira Cloud with your email and an API token or with OAuth through the browser, where the Cloud ID and refresh token are filled in automatically. Jira Server takes a user email and API token. A Token Server option stores refreshed OAuth tokens in a file or registry key, so scheduled packages keep running after the first token expires.
A Lookup that batches and caches
The Jira Lookup in Devart SSIS Data Flow Components for Jira checks several incoming rows at once and caches the returned results, which saves API calls when you match many rows against Jira issues or users.
Benefits
- No API code to maintain. Jira objects behave like tables in SSIS, and Devart keeps up with Jira's API.
- Reporting outside Jira. Issue data lands in SQL Server next to time, finance and CRM data.
- Two-way. The same tool reads issues and pushes changes back.
- Unattended runs. Stored refresh tokens let scheduled packages keep their OAuth sign-in.
Real-World Uses
- Delivery reporting. A nightly package copies issues, statuses and resolutions into SQL Server, where Power BI reports cycle time per project.
- Support tickets to Jira. A package reads escalated cases from a help desk database and creates Jira issues with the Destination.
- Bulk updates from a spreadsheet. A CSV of issue keys and new values updates hundreds of issues in one run.
- Matching people across systems. The Lookup checks incoming HR or CRM records against Jira users.
Who It's For, and Who Should Skip It
These components suit companies that run SSIS on SQL Server and want Jira data in their warehouse, or need to push records from other systems into Jira on a schedule.
Skip them if you don't use SSIS: Jira's own reports, its CSV export, Atlassian's marketplace apps or a cloud ETL service are simpler outside the Microsoft stack. If you only need Jira data in Excel or Power BI, Devart's ODBC Driver for Jira is a lighter fit.
Usage Guide
- Sign in to Devart (a free account), download the installer from the product's download page and run it; select the Jira components and the SSIS versions you use.
- Open an Integration Services project in Visual Studio. The Devart Jira components appear in the SSIS Toolbox.
- In Connection Managers, add a new Devart Jira connection: choose Cloud or Server, enter your Jira domain, then enter your email and API token, or click Sign In for OAuth on Jira Cloud.
- Drag a Devart Jira Source into a Data Flow task, pick an object in the editor or write a SELECT, and click Preview to check the rows.
- Connect the Source to a destination, or add a Devart Jira Destination to load rows into Jira, map the columns and run the package.
Before you buy
The Developer license covers development and testing on one developer's machines only. Running packages on a production SSIS server needs a Server license ($379.95 a year or $749.95 perpetual) or a Site license. Everything goes through Jira's REST API, which is slower than a database query, so a full export of many thousands of issues takes time; plan the first load and then pull only recently updated issues.
Where it falls short
- Complex SQL runs locally. Queries Jira's API can't answer are processed after fetching the data, which is slower on big sites.
- Custom fields need care. Same-named custom fields from different projects must be merged by a setting you choose.
- Windows and SSIS only. No use outside SQL Server Integration Services.
- Large download. The installer is over 600 MB even if you only want the Jira components.
- Few reviews. Only a dozen Capterra reviews cover the whole SSIS line, none of them about Jira specifically.
What Users Say
Capterra (whole SSIS line)
Review sites rate Devart's SSIS components as one product line, not the Jira components on their own. On Capterra, SSIS Data Flow Components average 4.6 out of 5 from 12 reviews, with 4.3 for ease of use and 4.3 for customer service. Reviewers are mostly BI specialists, database administrators and integrators. They describe the components as easy to set up inside Visual Studio and efficient for routine ETL work, and some picked them on price; the criticisms are occasional bugs, packages that grow hard to maintain over time, and a wish for more help with troubleshooting.
In short: what people like is the quick setup inside Visual Studio and the price compared with larger ETL suites; what they complain about is the odd bug and the effort of keeping big packages tidy. There are no published reviews of the Jira components alone, so run the trial against your own Jira site, with your own custom fields, before deciding.
Comparisons
Jira SSIS components vs. Devart's ODBC Driver for Jira
Devart also sells an ODBC Driver for Jira that serves Excel, Power BI and other ODBC tools. For ETL packages in SSIS, the SSIS components are the better fit, with a Jira Destination and Lookup built for data flows; for ad-hoc queries and reports outside SSIS, the driver is the one to buy.
Jira components vs. the SSIS Universal Bundle
The SSIS Universal Bundle ($499.95 a year or $999.95 perpetual) includes Jira along with more than 40 other sources such as Asana, Slack, Salesforce and HubSpot. If you need three or more sources, the bundle is the better deal; for Jira alone, these components cost far less.
Editions and Pricing
| License | 1-year subscription | Perpetual | What it covers |
|---|
| Developer | $149.95 | $299.95 | One developer's machines, for development and testing |
| Server | $379.95 | $749.95 | One server running packages, plus one developer |
| Site for 10-100 Devices | $499.95 | $999.95 | Unlimited computers in one company |
Buy Now opens the order page for SSIS Data Flow Components for Jira; you choose the license, subscription or perpetual, a 1-, 2- or 3-year term and optional premium support there. The SSIS Universal Bundle, with components for more than 40 sources including Jira, costs $499.95 a year or $999.95 perpetual on Devart's page.
FAQs
Do Devart's Jira SSIS components work with Jira Server as well as Jira Cloud?
Yes. The Devart Jira Connection Manager has an Environment setting for Cloud or Server. Jira Cloud accepts an email with an API token or OAuth sign-in; Jira Server takes a user email and API token.
Do I write JQL or SQL with Devart's Jira Source?
SQL. Devart SSIS Data Flow Components for Jira accept SELECT statements against tables such as Issues and translate simple ones into Jira API calls; more complex queries are processed locally.
Can Devart's SSIS components create Jira issues?
Yes. The Jira Destination in Devart SSIS Data Flow Components for Jira supports INSERT, UPDATE and DELETE, so a package can create, update or delete issues.
Will a scheduled package lose its Jira OAuth sign-in?
Not if you set the Token Server option. Devart SSIS Data Flow Components for Jira can store refreshed OAuth tokens in a file or registry key and request new ones automatically when the current token expires.
Which SSIS versions do the Jira components work with?
Devart SSIS Data Flow Components for Jira work with SQL Server Integration Services 2012, 2014, 2016, 2017, 2019, 2022 and 2025, on Windows Vista or later with .NET Framework 4.5.
Do I need a separate license for the production SSIS server?
Yes. The Developer license of SSIS Data Flow Components for Jira covers development and testing only; deploying packages to a server needs a Server license or a Site license.
What happens when the subscription ends?
The subscription license of SSIS Data Flow Components for Jira works for the term you paid for, so packages that use it need a renewal. A perpetual license keeps working at the version you have.
Can I get a refund?
Only for technical problems. Devart's ordering FAQ gives a full refund within 30 days of purchase when a bug or technical issue stops SSIS Data Flow Components for Jira working and support can't fix it. Use the 30-day trial against your own Jira site before buying.
System Requirements
- Microsoft SQL Server Integration Services 2012, 2014, 2016, 2017, 2019, 2022 or 2025
- Visual Studio with Integration Services projects for designing packages
- Windows Vista or later, 32-bit or 64-bit, with .NET Framework 4.5
- A Jira Cloud or Jira Server site, with an API token or OAuth sign-in
Conclusion
Devart SSIS Data Flow Components for Jira are worth $149.95 a year to SSIS teams that need Jira issues in SQL Server or want to push data into Jira on a schedule: you get SQL access to Jira objects, write-back, a sensible answer to cross-project custom fields and OAuth that survives unattended runs. Add a Server license for production. Without SSIS, Jira's own exports or Devart's ODBC driver are simpler, and if Jira is one of several sources, the Universal Bundle is better value.
Download Free Trial Buy Now