The reasons for running multiple instances varies depending on the use case.
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
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 theiHubapp. Get the app here:https://marketplace.atlassian.com/1220905
Synchronizing new issues from Jira A to Jira B
Start by installingiHubfrom 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)
Here, we're creating a basic auth for accessing the Jira B instance. Authentications are reusable and can be used for multiple integration actions.
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.
Select HTTP methodPOSTand enter the Jira B instance URL followed by/rest/api/2/createwhich is the Jira API endpoint for creating issues. (For convenience, iHub has templates that fill this in for you)
Select the authentication created in the previous step, here it'sJIRA B User[BASIC_AUTH]
Note:Make sure that the HTTP Headers haveContent-Typeset toapplication/json, if not, just add it manually.
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 newIntegrations Hub for Jiraaction.
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:https://doc.rixter.se/display/RIFJ/User+Guide
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!
REST integrations and automation for Jiraenablescustommade,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 theresponsefrom one asinputto 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.