Integration Hub for JIRA

Integration Hub for Jira short named i.hub is an automation tool for REST integrations. 

Solves common integration problems such as creating a ticket in another system and fetching data from external systems.

  • Uses the standard HTTP protocols to communicate with any arbitrary endpoint. 
  • Automated by event listener on issues and schedule jobs, defined by a cron expression.
  • Can retrieve and update external systems

When should I use Integrations Hub?  Use it for fetching data from other systems using REST calls. Use the response Use it to automate Jira 

The scenarios are endless, from communication with external systems as well as operating on the JIRA instance it is installed on.

Examples of systems that Integration Hub for Jira can integrate towards!

Warm welcome to submit a support request here: and we will add a tutorial for that system.

iHub is a multi purpose tool that can integrate any REST based system. Tutorials is just a quick guide to get started.

In this article, you will learn how to have two Jira instances synchronizing issues between each other using the "Integrations Hub for Jira" app.

The iHub can be downloaded here:

Why running multiple instances?

The reasons for running multiple instances varies depending on the use case.

For example:

  • Your company has separated customer support and development Jiras
  • You have an outsourced department using a separate Jira
  • You've merged with another company ending up in multiple Jira instances

The problem

Jira does not support synchronizing multiple instances out of the box, you will need a third-party app to do do this. This article will show you how to do this with the iHub app. Get the app here:

Synchronizing new issues from Jira A to Jira B

Start by installing iHub from the Atlassian Marketplace.

This is what we want to accomplish:

  • All Jira issues, in a project, that are created in "Jira A" shall be synchronized to "Jira B" and vice versa.
  • Synced issues shall be back referenced in "Jira A" for future tracking. (see syncing everything below)

Setup in Jira A: Authentications

First, create authentication for Jira B access.

The iHub has support for

  • Oauth2 (with support for authorization code, implicit, resource owner password, client credentials, and authorization code with assertion)
  • Basic auth
  • Bearer tokens

Here, we're creating a basic auth for accessing the Jira B instance. Authentications are reusable and can be used for multiple integration actions.

Integration configuration

Next, set up the configurations for syncing Jira A to Jira B.

Setting up integrations is easy, it's a no-code, user-friendly interface.

The iHub talks REST. We're using Jiras REST API to synchronize new issues to Jira B-instance.

  1. Select HTTP method POST and enter the Jira B instance URL followed by /rest/api/2/create which is the Jira API endpoint for creating issues. (For convenience, iHub has templates that fill this in for you)
  2. Select the authentication created in the previous step, here it's JIRA B User[BASIC_AUTH]

Note: Make sure that the HTTP Headers have Content-Type set to application/json, if not, just add it manually.

3. Fill in the fields that you want to set in the Jira B synched issue. Read more about the Jira API here:

Note how we access variables by using for the Mustache expression {{ issue }} This will get you access to the issue within this scope. (scope = issue that triggered this integration to run)

Access issue properties like this {{issue.summary}} to get the summary. {{}} to get the issue type name. All this is documented here:

Trigger configuration

For the synchronization to happen we need to set up a trigger. In this case, we will listen to all issue created events.

  1. Select "Issue Created" in the event triggers list. This will trigger this integration every time a new issue is created.
  2. Add a JQL condition to narrow the scope on which issues that are synced, or leave blank to sync everything. In this example were only synchronizing the project "SYNCIT"

That's it! Now all new issues in Jira A that are created in project SYNCIT will be posted to Jira B.

Saving issue key from Jira B

Since we most likely want to synchronize issue updates, comments, i.e. we need to store the issue key from the newly created issue in Jira B.

This is the response from the Jira B create issue API

Now, let's use this and update the triggering issue with the key from this response. This is done by creating a "child action".

A "child action" can use the response from its parent and do what it needs with it. It gets triggered after the parent has been triggered.

Create a new action, let's call SYNC - Set Reference

1. Select the "Auto-generate 1st level as variables from response". This will make the first level of json response available as variables.

In this example: id, key, self will be accessible by using Mustache templates ie. {{ key }}.

( If you need variables further down the json response you can specify a json path manually to get hold of that variable. )

2. Fill in the URL details, in this example, we're updating our parent issue using the Jira REST API.

HTTP method PUT, the URL is {{baseUrl}} /rest/api/2/issue/{{issue.key}}

3. Select an authentication that has access to Jira A (If no one exists, create one following the steps above)

5. Fill in the PUT body. Here we're using the {{ key }} variable auto-generated from 1 above.

That's it!

Now you're all set for synchronizing two Jira instances.

If you need advice on how to sync comments, updates, and transitions please feel free to reach out to us.

Get the app here:

This will be the first article in a series of articles on how to integrate Jira with other systems in less than 5 minutes.

I know that 5 minutes is not much, but if you have your ServiceNow instance up and running and know how to setup Oauth2 applications in ServiceNow you can do this in less than 3 minutes!

First, get the Jira app, "Integrations Hub for Jira" Get it here:

Second, create an Oauth2 connection to ServiceNow

  • In ServiceNow, create an Oauth2 application. Never done this before? Just follow our guide here: It's easy-peasy!
  • Now click the "lock" icon in the icon-menu, enter a name and click "Add authentication"

  • Select Authorization code and fill in your client id, secret ie.

Third, now create an integration action that uses this Oauth2 client to create a ServiceNow incident.

  • Click the "Create" button to create a new Integrations Hub for Jira action.

  • Fill in the form that pops up, use template "default" and content-type "application/json"

  • Fill in the integration details such as ServiceNow URL

  • The body section contains the POST body that goes to ServiceNow. In this example, we're posting the Jira Issues summary and description to ServiceNow. Read up on the full list of variables that can be used here:

And finally, set up how to trigger this integration.

  • Triggering an integration can be done in many various ways. Such as, a Jira event, schedule a cron job that runs this on a scheduled basis. From the post functions section, create a post-function or set up an incoming request rule that triggers this integration.
  • In this case, we have chosen to trigger this for all newly created Jira issues

Now, test your integration by creating a new Jira issue!

Happy hacking!

With our latest release of REST Integrations & Automations, it is super simple to create any OAuth integration without needing to code!

In this tutorial, I will describe how to do it with salesforce and some of the use cases that we see are common.

So we want to achieve this:

When an issue is created it sends that to Salesforce and updates the issue with the case number and status.

Secondly, we want to fetch the status of the case to find out if there has been any update. 

This can also be done on a periodic schedule by using the cron expression. (not covered in this article)

So were do we start?...

The first thing that needs to be done is to create what Salesforce calls a Connected app.

The important thing here is to select the right scope and to add the callback URL. This is always found on the OAuth authentication page in RINT.

Once this is done the next step is to set up the authentication in RINT.

In RINT we select the Authentication menu (lock icon) and enter the details that out Salesforce connected app returned. 

Note that state shall be check but leave the scope blank.

Once all the data is filled in click Authenticate and login to Salesforce. You will notice the two labels "Auth Code Granted" and "Access Token Granted" when all went good.

So now down to the actual REST call to do something in Salesforce based on JIRA data

Simply click Create and fill in a name and select the application / json as template to get the headers for free.

The request details can now be filled in, such as the method and url. Note for salesforce use the "" as url and not the

Now to where the actual JIRA data comes from

The body part of the form describes what data to send, RINT can send the issue data by simply using curly brackets and dot notation.




Trigger Time!

Once the data for the REST call is setup the only thing left is to add a Trigger to decide when to send the call.

We will use Issue Created with the condition limited to our SAL project.

This now means that the REST call to salesforce using the authentication that we setup will be triggered every time there is a new issue in our SAL project!

Yeah! but wait... how does it know to update the issue with the Case ID?

Now the chained actions come into play.

We will create a new action again this time we will use the "Select parent action" field to specify our previously created "Salesforce - Add case info"

Further on we can take some help by selecting the "JIRA Core Server" category and the "Edit Issue" template to speed things up.


What did we get now?

First, we can see that the tree now has a parent → Child for the salesforce part. Secondly, we can see that it created a new REST request to our JIRA server.

By selecting "Auto-generate 1st level as variables from parent response" we will automatically on this REST call get the response from the create case call as variables.

The response can be viewed by clicking on the Execution log on the "Salesforce - Add case info" action

So let's use what we know from the response to send that to the edit issue REST call.

As noted the {{id}} will automatically be replaced by the response from the parent once the chain is executed.

There's a new add-on in town! "REST integrations and automation for Jira" made by the add-on vendor Rixter.

REST integrations and automation for Jira enables custom made, no-code trigger-driven rest-integrations and automation.

During the engineering research, people have said: "This is the missing piece we've been looking for!".

So, what's the fuzz all about?

This addon gives you the power to create REST integrations and automation from an intuitive UI; no-code and scriptless. Triggered by an issue event or on a scheduled basis, all in the world of REST API's.

All your REST-integrations aka. "actions" can be chained, using the response from one as input to the next. Hence, the possibilities are endless!

The fact that Jira is exposing a REST API's this becomes extremely powerful, you can now automate your Jira instance in any way you want.

REST integrations and automation for Jira can be found at the Atlassian marketplace. Click here to Get it now!

Read more:

Happy integrations!

Table of content

Recently Updated