So, let’s get started.

Requirements

1. A first requirement will be to SQL Server Database Engine Installed
2. The second requirement will be SSMS installed
3. Finally, make sure to have ZappySys ODBC PowerPack installed.

What is JIRA

JIRA is Atlassian’s popular project- and issue-tracking platform used by development and technical support teams to get more work done and faster.

It combines:

issue tracking – a software application that allows to record and follow the progress of every problem or “issue” that user identifies until the problem is resolved.
agile project management – an iterative approach to planning and guiding project processes. customizable workflow, and a pluggable integration – integrates with Freshdesk, GitHub, Zendesk, Zapbook, Asana and so on.

Getting Started

First of all, we will see several examples. ZappySys includes an ODBC JSON Source Connector that will help you to call JIRA API, Insert issue in JIRA using static data from the SQL server using ODBC JSON driver REST API Call. Update and Delete JIRA issue data From the SQL Server. Insert Bulk JIRA issues from the stored procedure. To learn more about JIRA API check this help file.

About JIRA REST API

JIRA On-premises and Cloud Version both offers REST API. Here are some examples of JIRA REST API. For inserting issue in JIRA we will use JIRA REST API create issue method. We can also insert issues in bulk using Create issues bulk method. To update issue we will use this PUT method: Updating an Issue via the JIRA REST APIs. To delete issue we will use this DELETE method. You can find JIRA Rest API example on this link: Jira REST API examples

Step-by-Step: Write in JIRA from SQL Server

Now once you have API token in the JIRA Atlassian Cloud website we can move to ODBC JSON Driver Configuration Part. For this example purpose you can use the following URL:

https://YOUR-DOMAIN.atlassian.net/rest/api/2/issue/

hence, your-domain is your Atlassian Cloud account’s domain name (we are using zappysys2.atlassian.net).

Above all, each API endpoint may have a different limit for the number of items returned, and these limits may change without notice. (For more See this JIRA REST API reference)

Configure ZappySys Gateway data Source for JIRA

1. To do this, first of all, we will open the ZappySys Data Gateway Configuration:
   

   Open ZappySys Data Gateway

2. Add the Native – ZappySys JSON Driver Data source.
   

   Add Gateway Data Source (Native JSON Driver)

3. Now it’s time to connect with JIRA. Let’s use JSON Driver Data source with the following URL:
   

   https://YOUR-DOMAIN.atlassian.net/rest/api/2/issue/

   

   ODBC JSON Driver: Enter Request URL

4. It is time to configure the Other Settings. Select HTTP Connection Type from the Connection Type drop-down and Click on Click to Configure Link to Configure the Connection Manager.
   

   JIRA REST API Connection – Use ZappySys JSON Driver HTTP Connection

5. Now, Let’s Add request body input data of issue.
   

   {
       "fields": {
          "project":
          {
             "id": "<YOUR-PROJECT-ID>"
          },
          "summary": "No REST for the Wicked.",
          "description": "Creating of an issue using IDs for projects and issue types using the REST API",
          "issuetype": {
             "id": "<ISSUE-TYPE-ID>"
          }
      }
   }

   

   Issue Input Data

6. Now using Query Builder we will generate the query.
   

   Generate JIRA Rest API Post Method Query

7. Now Let’s Test Connection and it will prompt the message “Connection is OK!”
8. That’s it we have successfully configured JIRA Rest API in ODBC JSON Driver.

Setup Linked Server in MS SQL Server for JIRA

Once you configured the data source in Gateway, we can now setup Linked Server in SQL Server to query API Calls.

1. Assuming you have installed SQL Server and SSMS. If not then get both for FREE from here: Get SQL Server Express and  Get SSMS
2. Open SSMS and connect to SQL Server.
3. Go to Root > Server Objects > Linked Servers node. Right click and click New Linked Server…

   

   Add Linked Server in SQL Server

4.  Now enter the linked server name, select Provider as SQL Native Client
5. Enter data source as 

   GatewayServerName, PORT_NUMBER

    where server name is where ZappySys Gateway is running (Can be same as SQL Server machine or remote machine). Default PORT_NUMBER is 5000 but confirm on Data gateway > General tab in case its different.
6. Enter Catalog Name. This must match name from Data gateway Data sources grid > Name column

   

   Configure Linked Server Provider, Catalog, Server, Port for ZappySys Data Gateway Connection

7. Click on Security Tab and select last option “Be made using this security context“. Enter your gateway user account here.
8. Click OK to save Linked Server

Insert data in JIRA from SQL Server (Call POST API Method)

1. To Insert the issue in JIRA we need to execute the query like this. Please refer to this link for more information: Creating an issue example.
   
   Important Note*: If you don’t pass META='{xxxx}’ in query driver call REST API 2 times first time to parse metadata and second time to get actual data. So that you find some odd thing in JIRA project if you execute the query without Meta then you will find two same issues created in your JIRA project as the driver makes two calls as mentioned above.

   SELECT * FROM OPENQUERY([MY_LINKED_SERVER_NAME], 
   'SELECT * FROM $
   WITH( META=''[{"Name": "Success","Type": "Int32"}]''
        ,Src=''https://zappysys2.atlassian.net/rest/api/2/issue/''
        ,RequestData=''{
          "fields": {
           "project":
           {
             "id": "10110"
           },
           "summary": "No REST for the Wicked.",
           "description": "Creating of an issue using IDs for projects and issue types using the REST API",
           "issuetype": {
             "id": "1"
          }
        }
   }''
   ,Header=''Content-Type: application/json || Accept: */*''
   ,RequestMethod=''POST''
   )')

2. Here is the preview after you run REST API query in SQL Server. It will return created issue id, key, and Link. Now let’s note down this response to update and delete the same issue if you want to. Notice that you can override default configuration by supplying many parameters in WITH clause.
   

   Insert Issue In JIRA Using SQL Query

3. You can also find this created issue in your JIRA project.
   

   Created Issue in JIRA

Update data in JIRA from SQL Server (Call PUT API Method)

1. Let’s update the issue which we created in the previous step using id. I Added Extra Meta details in Query to prevent driver to make two calls and also to prevent error as JIRA Rest API Response is a blank

   Status code of "204 No Content"

   . Please refer to this link for more information: Updating an Issue via the JIRA REST APIs
   

   SELECT * FROM OPENQUERY([MY_LINKED_SERVER_NAME]
   , 'SELECT * FROM $
      WITH(META=''[{"Name": "Success","Type": "Int32"}]'' ,
   	 Src=''https://zappysys2.atlassian.net/rest/api/2/issue/10391''
   	,DataConnectionType=''HTTP''
   	,RequestData=''{
       "fields": {
          "summary": "Updated One!...Ye merry gentlemen."
      }
   }''
   	,Header=''Content-Type: application/json || Accept: */*''
   	,RequestMethod=''PUT''
   )')

2. Let’s is the preview after you running update query in SQL Server.
   

   Update Jira Issue From SQL Server

3. Now, Let’s see the updated issue in JIRA project.
   

   Updated Issue In JIRA Project

4. One Import note if you don’t add that metadata then you will get an error like below as JIRA Rest API Response is a blank “Status code of ‘204 No Content'”. If you don’t set META the REST API Make Two calls First to parse metadata and for the second time to get actual data.
   
   Query execution error: No data returned for specified table name or filter expression. Make sure table name or filter is typed correctly (it is case sensitive) and input data contains a corresponding element(s).

Delete data in JIRA from SQL Server (Call DELETE API Method)

1. Now let’s delete the issue which we created by executing following query in SQL Server. We also need to add extra meta details in query same as update one as JIRA Rest API Response is a blank

   Status code of "204 No Content"

   . Please refer to this link for more information: Delete an Issue via the JIRA REST API
   

   SELECT * FROM OPENQUERY([MY_LINKED_SERVER_NAME]
   , 'SELECT * FROM $
      WITH(META=''[{"Name": "Success","Type": "Int32"}]'' ,
   	 Src=''https://zappysys2.atlassian.net/rest/api/2/issue/10391''
   	,DataConnectionType=''HTTP''
   	,Header=''Content-Type: application/json || Accept: */*''
   	,RequestMethod=''DELETE''
   )')

2. Now, Let’s check the deleted issue in JIRA project.
   

   Issue Deleted in JIRA Project

Create multiple JIRA issues using SQL Server Stored Proc

Now lets put all previous things to more practical use. We will create a stored procedure which will read Issues stored in a SQL Table and Submit it to JIRA to create new Issue via REST API call. This will make it totally dynamic so SQL Table can act as your Source of information for API call.

1. Let’s create stored procedure to read data from “tblIssues” data table and create bulk issues in JIRA.
   

   alter PROCEDURE usp_AddMultipleJiraIssues
   AS
   BEGIN
   
   Declare @issueTemp nvarchar(2000)
   Declare @PostQuery nvarchar(MAX)
   Declare @strIssues nvarchar(MAX)
   set @PostQuery='';
   set @strIssues='';
   
   ---- Template 
   set @issueTemp=	'{
   			"fields": {
   				"project": {
   					"key": "<YOUR-JIRA-PROJECT-KEY>"
   				},
   				"summary": "[ISSUE-SUMMARY]",
   				"description": "[ISSUE-DESCRIPTION]",
   			        "issuetype": {
   					  "id": "<YOUR-JIRA-ISSUE-TYPE>"
   				}
   			}
   		}';
   
   -----Generate issues JSON String from the data table 
   Select @strIssues = @strIssues
                       + REPLACE(REPLACE(@issueTemp,'[ISSUE-SUMMARY]',isnull(i.summary,''))
                                                ,'[ISSUE-DESCRIPTION]',isnull(i.description,''))
                       + ',' 
   from tblissues i
   
   -----Trim last , comma from the string otherwise you will get an error 
   SET @strIssues = LEFT(@strIssues,(LEN(@strIssues)-1))
   
   -----JIRA Post Query
   SET @PostQuery= 'SELECT * FROM OPENQUERY([UPDATE_JIRA_DATA_JSON_DRIVER]
   					, ''SELECT * FROM $
   					WITH(
   						META=''''[{"Name": "Success","Type": "Int32"}]''''
                                                   ,Src=''''https://zappysys2.atlassian.net/rest/api/2/issue/bulk''''
   						,DataConnectionType=''''HTTP''''
   						,RequestData=''''{
   						   "issueUpdates": [' + @strIssues + ']
   					        }''''
   						,Header=''''Content-Type: application/json || Accept: */*''''
   						,RequestMethod=''''POST''''
   					)'')'
   
   --Print(@PostQuery)
   
   ----Posting issues data in JIRA
   Execute(@PostQuery)
   
   END
   GO

2. That’s it now executes the stored procedure and you will find bulk issues created in your JIRA project.
   

   Bulk Issues Created In Jira

Conclusion

In this blog, we learned how to generate a JIRA API Token and how to configure it,  Insert, Update and delete Issue in JIRA using ODBC JSON / REST API Driver from the SQL server. You can achieve many more functionalities with this tool. Check our blogs/articles on JSON / REST API Driver to find out what this tool is capable of more.

References

Finally, you can use the following links for more information about the use of JIRA API with our tools:

• JIRA Documentation for API
• Landing Page for ODBC JSON / REST API Driver, you can also find Tutorial Video here.
• Help File: Documentation of JSON Driver.
• Blog/articles link: https://zappysys.com/blog/category/odbc-powerpack/odbc-drivers/json-rest-api-driver/

The post Insert, Update and Delete JIRA Issue in SQL Server appeared first on ZappySys Blog.

We will go through the steps to read data from JIRA and Load into SQL Server using JSON Driver of ODBC PowerPack

In nutshell, this post will focus on how to call JIRA API using ODBC PowerPack and how to create SSRS Report.

So let’s get started.

Requirements

1. Make sure you have SSRS designer installed (You can download SSDT BI for Visual Studio).
2. Finally, make sure to have ZappySys ODBC PowerPack installed.

What is JIRA

JIRA is Atlassian’s popular project- and issue-tracking platform used by development and technical support teams to get more work done and faster.

It combines:

issue tracking – a software application that allows to record and follow the progress of every problem or “issue” that user identifies until the problem is resolved.
agile project management – an iterative approach to planning and guiding project processes. customizable workflow, and a pluggable integration – integrates with Freshdesk, GitHub, Zendesk, Zapbook, Asana and so on.

Getting Started

First of all, we will see several examples. ZappySys includes an SSIS JSON Source Connector that will help you to call JIRA API, read various data from JIRA with SSIS and do many more actions using REST API. To learn more about JIRA API check this help file.

https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER

https://YOUR-DOMAIN.atlassian.net/rest/api/2/search?startAt=0&maxResults=100&jql=project=MYPROJECT

Create and configure new SSRS Reports (Using ODBC Connection)

Let’s create a new SSRS project.

1. In SSRS, in a new Reporting Service Project, add a new Data Source:
   

   Add SSRS data source

2. Also, specify a name for the data source and in type select ODBC. Press Edit to select the ODBC connection for JSON and REST API and select the ZappySys Data Source name that we created before.
   

   Add ODBC JSON Data Source

3. Now let’s create a new SSRS report which uses the API data source we created in the previous section.
4. Right-click on the Reports node and click Add New Report (Wizard mode)
   

   Add new SSRS report

    

5. In New report, wizard window clicks on next button until you reach the step of query builder like below screen. Now Press the query builder button.
   Note: You can also copy and paste the query directly into the Query string box which we created in the previous phase.

   SELECT * FROM "issues"

   

   Query builder

6. Now, press the Add table icon and go to Views. Select issues(DATA) and press Add.
   

   SSRS Add Table

7. Now remove DATA. prefix from the query so that our query look’s like as below and Click Ok button:
   

   SELECT issues.* FROM issues

8. Now press Next Button and select Tabular Report Type and go to next in the following option until the completing wizard and specify a name for the report and finally press the Finish button.
9. Now click on the Preview a report. It shows the report and exports the REST API data to Word, Excel, PowerPoint, etc:
   

   SSRS Preview a Report

10. That’s all we have successfully imported the JIRA data in SSRS Reports (SQL Server Reporting Services).

Conclusion

In this blog, we have learned how to retrieve the data from JIRA using ODBC JSON Driver and then generated the SSRS Reports using those data with ODBC DSN in a very simple way. You can achieve many more functionalities with the use of ODBC PowerPack.

References

Finally, you can use the following links for more information about the use of JIRA API with our tools:

• JIRA Documentation for API
• Landing Page for ODBC JSON / REST API Driver, you can also find Tutorial Video here.
• Help File: Documentation of JSON Driver.
• Blog/articles link: https://zappysys.com/blog/category/odbc-powerpack/odbc-drivers/json-rest-api-driver/

The post Read JIRA data in SSRS Reports (SQL Server Reporting Services) appeared first on ZappySys Blog.

Power BI is a very popular Business Analytic tool used to get business information. It is very popular because it is easy to install, simple to learn and very intuitive. Also, REST API is very popular these days and we wanted to show you a way to integrate them in Power BI with the help of the ZappySys ODBC PowerPack. This software includes powerful drivers to query REST API URL, Local XML / JSON files and XML SOAP Web Service with simple SQL queries.

In nutshell, this post will focus on how to call JIRA API using Zappysys ODBC PowerPack. So let’s get started

Prerequisite

1. First, you will need to have our ZappySys ODBC Power Pack.
2. In the second place, you will need to have internet access.
3. On third place, Power BI Desktop (FREE) installed.
4. JIRA Atlassian account.

What is JIRA

JIRA is Atlassian’s popular project- and issue-tracking platform used by development and technical support teams to get more work done and faster.

It combines:

issue tracking – a software application that allows to record and follow the progress of every problem or “issue” that user identifies until the problem is resolved.
agile project management – an iterative approach to planning and guiding project processes. customizable workflow, and a pluggable integration – integrates with Freshdesk, GitHub, Zendesk, Zapbook, Asana and so on.

Getting Started

In order to start, we will show several examples. ZappySys ODBC PowerPack includes the ZappySys JSON Driver that will help you to call JIRA API, retrieve various data from JIRA and load that data in Power BI. To learn more about JIRA API check this help file.

https://jira.atlassian.com/rest/api/2/search?jql=project=JRASERVER

https://YOUR-DOMAIN.atlassian.net/rest/api/2/search?startAt=0&maxResults=100&jql=project=MYPROJECT

Load JIRA data into Power BI (Connect JIRA REST API)

Conclusion

In this blog, we have learned how to retrieve the data from JIRA using ODBC JSON Driver and then Load those data in Power BI with ODBC DSN in a very simple way. You can achieve many more functionalities with the use of ODBC PowerPack.

References

Finally, you can use the following links for more information about the use of JIRA API with our tools:

• JIRA Documentation for API
• Landing Page for ODBC JSON / REST API Driver, you can also find Tutorial Video here.
• Help File: Documentation of JSON Driver.
• Blog/articles link: https://zappysys.com/blog/category/odbc-powerpack/odbc-drivers/json-rest-api-driver/

The post How to Import JIRA data in Power BI appeared first on ZappySys Blog.

We will go through the steps to read data from JIRA and Load into SQL Server using SSIS JSON Source Connector.

In nutshell, this post will focus on how to call JIRA API using SSIS.

So let’s get started.

Prerequisite

1. First, you will need to have SSIS installed
2. Secondly, make sure to have SSDT
3. Finally, do not forget to install ZappySys SSIS PowerPack

What is JIRA

JIRA is Atlassian’s popular project- and issue-tracking platform used by development and technical support teams to get more work done and faster.

It combines:

issue tracking – a software application that allows to record and follow the progress of every problem or “issue” that user identifies until the problem is resolved.
agile project management – an iterative approach to planning and guiding project processes. customizable workflow, and a pluggable integration – integrates with Freshdesk, GitHub, Zendesk, Zapbook, Asana and so on.

Getting Started

In order to start, we will show several examples. ZappySys includes an SSIS JSON Source Connector that will help you to call JIRA API, read various data from JIRA with SSIS and do many more actions using REST API. To learn more about JIRA API check this help file.

Load JIRA data to SQL Server using SSIS JSON Source

Now once you have API token in the JIRA Atlassian Cloud website we can move to SSIS Part.

1. Create a new SSIS Project or Open Existing Project in Visual Studio  (File > New > Project > Business Intelligence > Integration Services)
2. Once SSIS Package is open, Goto Data Flow Section, Drag and Drop ZS JSON Source Component from the SSIS Toolbox.
   

   Drag and Drop JSON Source Component

3. Double click on that Component to Edit the Configurations. Select File path or web URL from the Access Mode drop-down.
   Enter Web URL like this:
   

   https://your-domain.atlassian.net/rest/api/2/search?startAt=0&maxResults=50

   Here, your-domain is your Atlassian Cloud account’s domain name (we are using zappysys.atlassian.net).

   * startAt is the index of the first item returned in the page of results.
   * maxResults the maximum number of items that can be returned per page. Each API endpoint may have a different limit for the number of items returned, and these limits may change without notice. (For more See this JIRA API Documentation for Pagination)

   

   JSON Source: Enter the Request URL

4. Check Use Credentials Option and select a new ZS-HTTP Connection from the drop-down.
5. Configure new HTTP Connection for JIRA as below.
   Basically, you need to enter 3 pieces on the General tab (i.e. Auth URL, Atlassian Account UserName, API token)
   

   JIRA Connection: HTTP Connection Manager

6. now, we are going to set Pagination related configurations for JIRA Search request. For example, if you want to read 50 records in each response and keep doing it until last page found then set startAt=0, maxResults=50 and increment startAt by 50.
   
   Do not to submit your App for Marketplace Approval (Last step) if you are creating OAuth App to access their own company data and do not want to access other company’s data using your app. In other words leave your app under Development mode only (Ignore production credentials if you do not wish to publish app to marketplace).
   

   JSON Source – JIRA request Pagination Configurations Settings

7. Select Filter, Click on the Preview button to see the response data.
   

   JSON Source: Preview Issues/tickets of JIRA

8. Click OK to save JSON Source settings.
9. Drag any destination (i.e. OLEDB Destination) from your SSIS toolbox. For demo purpose, we will load JIRA Issues data into SQL Server Table.
   

   Drag and Drop OLE DB Destination Component

10. Configure OLEDB Destination (Select Connection and Target Table). You can Create a new Table for the destination by clicking NEW next to Table drop-down.
    

    OLE DB Destination Component – Configure for dumping JIRA data in SQL Table

11. Click on the Columns Tab to configure Mappings. Click OK to save.
    

    OLE DB Destination – Column Configurations

12. You can see the requests in Fiddler.
    

    Fiddler – See All The Requests

13. And that’s it. Execute your package to Load JIRA data to SQL Server.

Conclusion

In this blog, we learned how to Generate a JIRA API Token, retrieve JIRA Issues/tickets data from JIRA with SSIS using ZS JSON Source Component in a very simple way. You can achieve many more functionalities with this tool. Check our blogs/articles on JSON Source Component https://zappysys.com/blog/tag/ssis-json-source/ to find out what this tool is capable of more.

References

Finally, you can use the following links for more information about the use of JIRA API with our tools:

• JIRA Documentation for API
• Landing Page for JSON Source Component, you can also find Tutorial Video here.
• Help File: Documentation of JSON Source Component.

The post How to read JIRA data in SSIS – Call REST API / Load to SQL Server appeared first on ZappySys Blog.