Jira Connectors

ZappySys Jira Connector provide read / write capability inside your app (see list below), using these drag and drop , high performance connectors you can perform many Jira operations without any coding. You can use this connector to integrate Jira data inside apps like SSIS, SQL Server or popular ETL Platforms / BI Tools/ Reporting Apps / Programming languages (i.e. Informatica, Power BI, SSRS, Excel, C#, JAVA, Python)

Download for SSIS Download for Other Apps Documentation

Video Tutorial - Jira - Connectors REST API Integration

Click on your App below to get started with Jira Integration

Choose your App / Scenario for which you like to integrate Jira

SSIS

SQL Server

Power BI

SSRS

Informatica

MS Access

MS Excel

SSAS

Python

JAVA

Tableau

SAP Crystal Reports

Azure Data Factory (ADF)

ODBC

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 => 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