SSRS Jira Connector

In this article you will learn how to integrate Jira data to SSRS without coding in just a few clicks (live / bi-directional connection to Jira). Jira Connector can be used to integrate Jira and your defined data source, e.g. Microsoft SQL, Oracle, Excel, Power BI, etc. Get, write, delete Issues, Users, Worklogs, Comments just in a few clicks!.

Using Jira Connector you will be able to connect, read, and write data from within SSRS. Follow the steps below to see how we would accomplish that.

Download  Help File  Buy 

See also
Jira Connector Connect Jira in SSIS SSIS
Connect Jira in SSIS
Jira Connector Connect Jira in SQL Server SQL Server
Connect Jira in SQL Server
Jira Connector Connect Jira in Power BI Power BI
Connect Jira in Power BI
Jira Connector Connect Jira in Informatica Informatica
Connect Jira in Informatica
Jira Connector Connect Jira in MS Access MS Access
Connect Jira in MS Access
Jira Connector Connect Jira in MS Excel MS Excel
Connect Jira in MS Excel
Jira Connector Connect Jira in SSAS SSAS
Connect Jira in SSAS
Jira Connector Connect Jira in C# C#
Connect Jira in C#
Jira Connector Connect Jira in Python Python
Connect Jira in Python
Jira Connector Connect Jira in JAVA JAVA
Connect Jira in JAVA
Jira Connector Connect Jira in Tableau Tableau
Connect Jira in Tableau
Jira Connector Connect Jira in SAP Crystal Reports SAP Crystal Reports
Connect Jira in SAP Crystal Reports
Jira Connector Connect Jira in Azure Data Factory (ADF) Azure Data Factory (ADF)
Connect Jira in Azure Data Factory (ADF)
Jira Connector Connect Jira in ODBC ODBC
Connect Jira in ODBC

Video Tutorial - Integrate Jira data in SSRS

This video covers following and more so watch carefully. After watching this video follow the steps described in this article.

  • How to download / install required driver for Jira integration in SSRS
  • How to configure connection for Jira
  • Features about API Driver (Authentication / Query Language / Examples / Driver UI)
  • Using Jira Connection in SSRS

Create Data Source in ZappySys Data Gateway based on ZappySys API Driver

  1. Download and install ZappySys ODBC PowerPack.

  2. Search for gateway in start menu and Open ZappySys Data Gateway:
    Open ZappySys Data Gateway

  3. Go to Users Tab to add our first Gateway user. Click Add; we will give it a name tdsuser and enter password you like to give. Check Admin option and click OK to save. We will use these details later when we create linked server:
    ZappySys Data Gateway - Add User

  4. Now we are ready to add a data source. Click Add, give data source a name (Copy this name somewhere, we will need it later) and then select Native - ZappySys API Driver. Finally, click OK. And it will create the Data Set for it and open the ZS driver UI.

    JiraDSN

    ZappySys Data Gateway - Add Data Source

  5. When the Configuration window appears give your data source a name if you haven't done that already, then select "Jira" from the list of Popular Connectors. If "Jira" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

    JiraDSN
    Jira
    ODBC DSN Template Selection

  6. Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

     API Key based Authentication [Http]

    Steps to get Jira Credentials
    Firstly, login into your Atlassian account and then go to your Jira profile:

    1. Go to Profile > Security.
    2. Click Create and manage API tokens.
    3. Then click Create API token button and give your token a label.
    4. When window appears with new API token, copy and use it in this connection manager.
    5. That's it!

    Fill in all required parameters and set optional parameters if needed:

    JiraDSN
    Jira
    API Key based Authentication [Http]
    https://[$Subdomain$].atlassian.net/rest/api/3
    Required Parameters
    Subdomain Fill in the parameter...
    Atlassian User Name (email) Fill in the parameter...
    API Key Fill in the parameter...
    Optional Parameters
    CustomColumnsRegex Fill in the parameter...
    ODBC DSN HTTP Connection Configuration

     OAuth based Authentication [OAuth]

    OAuth App must be created in Atlassian Developer Console. It is found at https://developer.atlassian.com/console/myapps/ [Read more..]

    Steps to get Jira Credentials
    Firstly, login into your Atlassian account and then create Jira application:

    1. Go to Atlassian Developer area.
    2. Click Create app and select OAuth 2.0 (3LO) integration app to create an OAuth app.
    3. Give your app a name, accept the terms and hit Create.
    4. Then hit App details panel and copy paste Client ID and Secret into the API Connection Manager configuration grid into the proper places.
    5. Then go back and click Permissions panel to enable permissions/scopes for your application. You can enable them all.
    6. Go back again to application settings and click Authorization panel.
    7. Click Configure button and in Callback URL enter your own Callback URL or simply enter https://zappysys.com/oauth if you don't have one.
    8. Use this same Callback URL (Return URL) in a API Connection Manager configuration grid.
    9. In API Connection Manager enter one or more of these scopes (read more about available scopes) into Scopes property:
      1. offline_access (a must)
      2. read:jira-user
      3. read:jira-work
      4. write:jira-work
      5. manage:jira-project
      6. manage:jira-configuration
    10. Also configure your company's Subdomain in the properties grid.
    11. Click Generate Token to generate tokens.
    12. That's it!

    Fill in all required parameters and set optional parameters if needed:

    JiraDSN
    Jira
    OAuth based Authentication [OAuth]
    https://[$Subdomain$].atlassian.net/rest/api/3
    Required Parameters
    ClientId Fill in the parameter...
    ClientSecret Fill in the parameter...
    Scope Fill in the parameter...
    ReturnUrl Fill in the parameter...
    Organization Id (Select after clicking [Generate Token]) Fill in the parameter...
    Optional Parameters
    Custom Columns for output (Select after clicking [Generate Token]) Fill in the parameter...
    ODBC DSN Oauth Connection Configuration

  7. Once the data source has been configured, you can preview data. Select the Preview tab and use settings similar to the following to preview data:
    ODBC ZappySys Data Source Preview

  8. Click OK to finish creating the data source.

Read data in SSRS from ZappySys Data Gateway

  1. Open Visual Studio and create a new SSRS project
  2. Then add a new Shared Data Source (you can create a non-shared data source inside report too): Adding a Data Source in SSRS project
  3. Continue with creating the Shared Data Source. Select Microsoft SQL Server as Type and hit Build button to proceed further: Configuring a Data Source to access API data in SSRS project
  4. Once a window opens, configure it similarly. Configure "JiraDSN" as database name. Finally, hit Test Connection and OK:
    JiraDSN
    Configuring thoroughly a Data Source to access API data in SSRS project
  5. Another window opens, and it should look similarly to this one below which ends the creation of a Data Source: How Data Source in SSRS project looks like
  6. Now it's time to create a Dataset. If you don't have a report created, in one of the wizard's steps it will look like this: Specifying a query in SSRS Dataset to access API data #1
  7. If you did not follow through report's creation wizard and already had report created, you can simply add a new dataset: Specifying a query in SSRS Dataset to access API data #2
  8. Finally, once you complete the report, similar results show up: ZappySys Data Gateway API data source results

Passing Parameters to SSRS Report / Filter data

If you want to parameterized your report then refer to this article

Create Custom Store Procedure in ZappySys Driver

You can create procedures to encapsulate custom logic and then only pass handful parameters rather than long SQL to execute your API call.

Steps to create Custom Store Procedure in ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here

  1. Go to Custom Objects Tab and Click on Add button and Select Add Procedure:
    ZappySys Driver - Add Store Procedure

  2. Enter the desired Procedure name and click on OK:
    ZappySys Driver - Add Store Procedure Name

  3. Select the created Store Procedure and write the your desired store procedure and Save it and it will create the custom store procedure in the ZappySys Driver:
    Here is an example stored procedure for ZappySys Driver. You can insert Placeholders anywhere inside Procedure Body. Read more about placeholders here 

    CREATE PROCEDURE [usp_get_orders]
    @fromdate = '<<yyyy-MM-dd,FUN_TODAY>>'
 AS
    SELECT * FROM Orders where OrderDate >= '<@fromdate>';

    ZappySys Driver - Create Custom Store Procedure

  4. That's it now go to Preview Tab and Execute your Store Procedure using Exec Command. In this example it will extract the orders from the date 1996-01-01: 

    Exec usp_get_orders '1996-01-01';

    ZappySys Driver - Execute Custom Store Procedure

  5. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder. 

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  6. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Create Custom Virtual Table in ZappySys Driver

ZappySys API Drivers support flexible Query language so you can override Default Properties you configured on Data Source such as URL, Body. This way you don't have to create multiple Data Sources if you like to read data from multiple EndPoints. However not every application support supplying custom SQL to driver so you can only select Table from list returned from driver.

Many applications like MS Access, Informatica Designer wont give you option to specify custom SQL when you import Objects. In such case Virtual Table is very useful. You can create many Virtual Tables on the same Data Source (e.g. If you have 50 URLs with slight variations you can create virtual tables with just URL as Parameter setting.

  1. Go to Custom Objects Tab and Click on Add button and Select Add Table:
    ZappySys Driver - Add Table

  2. Enter the desired Table name and click on OK:
    ZappySys Driver - Add Table Name

  3. And it will open the New Query Window Click on Cancel to close that window and go to Custom Objects Tab.

  4. Select the created table, Select Text Type AS SQL and write the your desired SQL Query and Save it and it will create the custom table in the ZappySys Driver:
    Here is an example SQL query for ZappySys Driver. You can insert Placeholders also. Read more about placeholders here 

    SELECT
  "ShipCountry",
  "OrderID",
  "CustomerID",
  "EmployeeID",
  "OrderDate",
  "RequiredDate",
  "ShippedDate",
  "ShipVia",
  "Freight",
  "ShipName",
  "ShipAddress",
  "ShipCity",
  "ShipRegion",
  "ShipPostalCode"
FROM "Orders"
Where "ShipCountry"='USA'

    ZappySys Driver - Create Custom Table

  5. That's it now go to Preview Tab and Execute your custom virtual table query. In this example it will extract the orders for the USA Shipping Country only: 

    SELECT * FROM "vt__usa_orders_only"

    ZappySys Driver - Execute Custom Virtual Table Query

  6. Let's generate the SQL Server Query Code to make the API call using store procedure. Go to Code Generator Tab, select language as SQL Server and click on Generate button the generate the code.
    As we already created the linked server for this Data Source, in that you just need to copy the Select Query and need to use the linked server name which we have apply on the place of [MY_API_SERVICE] placeholder. 

    SELECT * FROM OPENQUERY([MY_API_SERVICE], 'EXEC [usp_get_orders] ''1996-01-01''')

    ZappySys Driver - Generate SQL Server Query

  7. Now go to SQL served and execute that query and it will make the API call using store procedure and provide you the response.
    ZappySys Driver - Generate SQL Server Query

Conclusion

In this article we discussed how to connect to Jira in SSRS and integrate data without any coding. Click here to Download Jira Connector for SSRS and try yourself see how easy it is. If you still have any question(s) then ask here or simply click on live chat icon below and ask our expert (see bottom-right corner of this page).

Download Jira Connector for SSRS Documentation 

Actions supported by Jira Connector

Jira Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.
 Read Resources
 Read Fields
Parameter Description
 Read Custom Fields
Parameter Description
CustomColumnsRegex Enter regular expression for custom columns which you like to output. Use Pipe to type keys (internal names for columns). You can use Regex too (e.g. field_100\d+ )
 Read Issue Types
 Read Users
Parameter Description
 Create User
 Delete User
Parameter Description
AccountId
 Read Projects
 Create Project
 Upsert Project
Parameter Description
ProjectIdOrKey
 Delete Project
Parameter Description
ProjectIdOrKey Project ID or Key, uniquely representing a project
EnableUndo
 Read Issues
 Create Issues
 Update Issue
Parameter Description
IssueIdOrKey Enter Issue ID or Key
NotifyUsers Whether a notification email about the issue update is sent to all watchers. Possible values: true, false
OverrideScreenSecurity Whether screen security should be overridden to enable hidden fields to be edited. Possible values: true, false
OverrideEditableFlag Whether screen security should be overridden to enable uneditable fields to be edited. Possible values: true, false
 Delete Issue
Parameter Description
IssueIdOrKey Enter Issue ID or Key
 Read Worklogs
 Create Worklog
 Update Worklog
Parameter Description
IssueIdOrKey
WorklogId
 Delete Worklog
Parameter Description
IssueIdOrKey
WorklogId
 Read Comments
 Read Changelogs
Returns a paginated list of all changelogs for an issue sorted by date, starting from the oldest. OAuth scopes required: read:issue-meta:jira, read:avatar:jira, read:issue.changelog:jira
Parameter Description
IssueId Or Key
 Read Changelog Details
Returns a paginated list of all changelogs and fields updated for an issue sorted by date, starting from the oldest. OAuth scopes required: read:issue-meta:jira, read:avatar:jira, read:issue.changelog:jira
Parameter Description
IssueId Or Key
 Read Changelogs by IDs
Returns changelogs for an issue specified by a list of changelog IDs. OAuth scopes required: read:issue-meta:jira, read:avatar:jira, read:issue.changelog:jira
Parameter Description
IssueId Or Key
Comma Separated ChangeLog Ids
 Read Get custom field contexts Details
Returns a paginated list list of contexts for a custom field. OAuth scopes required: read:field:jira, read:custom-field-contextual-configuration:jira
Parameter Description
FieldId
 Read Get custom field contexts Details
Returns a paginated list of all custom field option for a context. Options are returned first then cascading options, in the order they display in Jira. OAuth scopes required: read:field.option:jira
Parameter Description
FieldId
ContextId
 Generic Request
This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL.
Parameter Description
Url API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
Body Request Body content goes here
IsMultiPart Check this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header =&gt; Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract
Headers Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Other App Integration scenarios for Jira

Jira Connector for SSIS
SSIS
Jira Connector for SQL Server
SQL Server
Jira Connector for Power BI
Power BI
Jira Connector for Informatica
Informatica
Jira Connector for MS Access
MS Access
Jira Connector for MS Excel
MS Excel
Jira Connector for SSAS
SSAS
Jira Connector for C#
C#
Jira Connector for Python
Python
Jira Connector for JAVA
JAVA
Jira Connector for Tableau
Tableau
Jira Connector for SAP Crystal Reports
SAP Crystal Reports
Jira Connector for Azure Data Factory (ADF)
Azure Data Factory (ADF)
Jira Connector for ODBC
ODBC

Other Connectors for SSRS

Zendesk Connector
Zendesk
Azure DevOps Connector
Azure DevOps
ManagedEngine ServiceDesk Plus (Zoho) Connector
ManagedEngine ServiceDesk Plus (Zoho)
Zoho CRM Connector
Zoho CRM
Hubspot Connector
Hubspot
Google Sheets Connector
Google Sheets
Stripe Connector
Stripe
YouTube Connector
YouTube
Google BigQuery Connector
Google BigQuery
OneDrive Connector
OneDrive
OData Connector
OData
Amazon Ads Connector
Amazon Ads
Mailchimp Connector
Mailchimp
Jira Connector
Jira
Outlook Mail (Office 365) Connector
Outlook Mail (Office 365)
Zoom Connector
Zoom
Cosmos DB Connector
Cosmos DB
Shopify Connector
Shopify
Nativo Connector
Nativo
Google Drive Connector
Google Drive
SharePoint Online Connector
SharePoint Online
Amazon MWS Connector
Amazon MWS
ServiceNow Connector
ServiceNow
ElasticSearch Connector
ElasticSearch
Google Calendar Connector
Google Calendar
DropBox Connector
DropBox
REST API Connector
REST API
JSON Connector
JSON
JSON File Connector
JSON File
XML Connector
XML
SOAP Connector
SOAP
XML File Connector
XML File
JDBC-ODBC Bridge Connector
JDBC-ODBC Bridge
Salesforce Connector
Salesforce
CSV Connector
CSV
Amazon S3 JSON File Connector
Amazon S3 JSON File
Amazon S3 XML File Connector
Amazon S3 XML File
Amazon S3 CSV File Connector
Amazon S3 CSV File
Azure Blob JSON File Connector
Azure Blob JSON File
Azure Blob XML File Connector
Azure Blob XML File
Azure Blob CSV File Connector
Azure Blob CSV File
FTP/SFTP JSON File Connector
FTP/SFTP JSON File
FTP/SFTP XML File Connector
FTP/SFTP XML File
FTP/SFTP CSV File Connector
FTP/SFTP CSV File


Download Jira Connector for SSRS Documentation 

  • How to connect Jira in SSRS?

  • How to get Jira data in SSRS?

  • How to read Jira data in SSRS?

  • How to load Jira data in SSRS?

  • How to import Jira data in SSRS?

  • How to pull Jira data in SSRS?

  • How to push data to Jira in SSRS?

  • How to write data to Jira in SSRS?

  • How to POST data to Jira in SSRS?

  • Call Jira API in SSRS

  • Consume Jira API in SSRS

  • Jira SSRS Automate

  • Jira SSRS Integration

  • Integration Jira in SSRS

  • Consume real-time Jira data in SSRS

  • Consume realtime Jira API data in SSRS

  • Jira ODBC Driver | ODBC Driver for Jira | ODBC Jira Driver | SSIS Jira Source | SSIS Jira Destination

  • Connect Jira in SSRS

  • Load Jira in SSRS

  • Load Jira data in SSRS

  • Read Jira data in SSRS

  • Jira API Call in SSRS