---
title: "Connect another Jira instance to BigPicture"
canonical: "https://support.appfire.com/space/SPM/2214658323/Connect%20another%20Jira%20instance%20to%20BigPicture"
format: markdown
---
> Macro (aura-html)
> ⚠️ New connections between Jira instances are temporarily unavailable. If you have already configured multiple Jira instances, your existing connections will continue to work. However, you cannot create new connections at this time.
## Connect another Jira instance to BigPicture (old navigation)
Expand
Connecting another instance allows BigPicture on your primary instance to integrate data from more than one Jira instance. The process involves setting up a connection in BigPicture and configuring a webhook on the secondary Jira Cloud instance.
To use additional Jira Clouds, you need to:
- connect them to the app
- add them to the scope of your boxes
**Steps required to add another Jira Cloud instance:**
## Initiate the Connection in BigPicture (Primary Instance)
1. Navigate to **App settings** → **Integrations** → **Connections** within BigPicture on your primary Jira Cloud instance (`nostromo6` in this example).
2. Click the **+ Add new connection** option.
3. Choose the **Jira Cloud** option.
> Macro (iframe)
4. You can also initiate adding an instance in box configuration → Tasks → Scope definition:
> Macro (iframe)
## Configure the New Connection Details in BigPicture
1. Provide a name for the new connection (in this example, `nostromo 13`).
2. Enter the URL of the secondary Jira Cloud instance you want to connect. This URL can be copied from the browser's address bar for the secondary instance.
3. Enter the email address associated with the user account you will use for the connection on the secondary instance.
4. You will need an API token from the secondary Jira Cloud instance. Leave this field ready for the next step (keep the
## Generate an API Token on the Secondary Jira Cloud Instance
1. Go to: [id.atlassian.com/manage-profiles/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens) . Log in with your Atlassian credentials.
2. Choose the **Create a new API token** option. Choose name and expiration date.
> ⚠️ **Important:** API tokens have a maximum lifespan of one year. To maintain the connection, you must renew the token before it expires. The connection isn't permanent after setting it up once; the token needs renewal.
3. Copy this token immediately, as once the window is closed, you cannot retrieve it later. It is recommended to paste it into a temporary location like a notepad.
> Macro (iframe)
## Paste the Token and Proceed in BigPicture
1. Return to the BigPicture connection setup page on your primary instance.
2. Paste the copied API token into the designated field.
3. Click **Next**.
4. After clicking next, BigPicture will request an **endpoint URL** for a webhook.
## Create the Webhook on the Secondary Jira Cloud Instance
> ⚠️ This webhook needs to be created on the **secondary** Jira Cloud instance.
1. Return to the secondary Jira Cloud instance browser tab.
2. Navigate to **Jira settings** → **System** and then **WebHooks**.
3. Click to **Create a WebHook**.
4. Name the webhook (for example,`connection to nostromo6`).
5. Ensure the webhook is **enabled**.
6. Paste the **endpoint link generated by the app** (the URL provided by BigPicture in the previous section) into the URL field.
7. Select all the checkbox of the events that should trigger the webhook.
8. The exception is **Exclude body**, which should be left **unchecked**.
9. **Create** (or save) the webhook.
> Macro (iframe)
## Complete the Connection in BigPicture
1. Return to the BigPicture connection setup page on your primary instance.
2. Click **Connect**.
3. If you get an error, you likely need to **go back one step** in the BigPicture setup and then click **Connect** again to ensure BigPicture recognizes the newly created webhook.
4. Proceed through the steps again. The connection process should successfully proceed with the webhook now registered on the secondary instance.
## Subsequent Steps (Field Mapping and Scope Definition)
1. Once the connection is successful, you will encounter further configuration steps within BigPicture, such as **field mapping** and **scope definition**.
1. **Field mapping** is not automatically created or copied, therefore you have to configure field mapping for each newly connected Jira instance. For more information, go to [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918700586](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918700586)
2. **Scope definition** - when another Jira Cloud instance is added to the app, you can add it to a box scope in box configuration and define scope’s details:
> Macro (iframe)
## Connect another Jira instance to BigPicture (new navigation)
Expand
Connecting another instance allows BigPicture on your primary instance to integrate data from more than one Jira instance. The process involves setting up a connection in BigPicture and configuring a webhook on the secondary Jira Cloud instance.
To use additional Jira Clouds, you need to:
- connect them to the app
- add them to the scope of your boxes
**Steps required to add another Jira Cloud instance:**
## Initiate the Connection in BigPicture (Primary Instance)
1. Navigate to **App settings** → **Integrations** → **Connections** within BigPicture on your primary Jira Cloud instance (`nostromo6` in this example).
2. Click the **+ Add new connection** option.
3. Choose the **Jira Cloud** option.
> Macro (iframe)
4. You can also initiate adding an instance in box configuration → Tasks → Work items from Jira:
> Macro (iframe)
## Configure the New Connection Details in BigPicture
1. Provide a name for the new connection (in this example, `nostromo 13`).
2. Enter the URL of the secondary Jira Cloud instance you want to connect. This URL can be copied from the browser's address bar for the secondary instance.
3. Enter the email address associated with the user account you will use for the connection on the secondary instance.
4. You will need an API token from the secondary Jira Cloud instance. Leave this field ready for the next step (keep the
## Generate an API Token on the Secondary Jira Cloud Instance
1. Go to: [id.atlassian.com/manage-profiles/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens) . Log in with your Atlassian credentials.
2. Choose the **Create a new API token** option. Choose name and expiration date.
> ⚠️ **Important:** API tokens have a maximum lifespan of one year. To maintain the connection, you must renew the token before it expires. The connection isn't permanent after setting it up once; the token needs renewal.
3. Copy this token immediately, as once the window is closed, you cannot retrieve it later. It is recommended to paste it into a temporary location like a notepad.
> Macro (iframe)
## Paste the Token and Proceed in BigPicture
1. Return to the BigPicture connection setup page on your primary instance.
2. Paste the copied API token into the designated field.
3. Click **Next**.
4. After clicking next, BigPicture will request an **endpoint URL** for a webhook.
## Create the Webhook on the Secondary Jira Cloud Instance
> ⚠️ This webhook needs to be created on the **secondary** Jira Cloud instance.
1. Return to the secondary Jira Cloud instance browser tab.
2. Navigate to **Jira settings** → **System** and then **WebHooks**.
3. Click to **Create a WebHook**.
4. Name the webhook (for example,`connection to nostromo6`).
5. Ensure the webhook is **enabled**.
6. Paste the **endpoint link generated by the app** (the URL provided by BigPicture in the previous section) into the URL field.
7. Select all the checkbox of the events that should trigger the webhook.
8. The exception is **Exclude body**, which should be left **unchecked**.
9. **Create** (or save) the webhook.
> Macro (iframe)
## Complete the Connection in BigPicture
1. Return to the BigPicture connection setup page on your primary instance.
2. Click **Connect**.
3. If you get an error, you likely need to **go back one step** in the BigPicture setup and then click **Connect** again to ensure BigPicture recognizes the newly created webhook.
4. Proceed through the steps again. The connection process should successfully proceed with the webhook now registered on the secondary instance.
## Subsequent Steps (Field Mapping and Scope Definition)
1. Once the connection is successful, you will encounter further configuration steps within BigPicture, such as **field mapping** and **scope definition**.
1. **Field mapping** is not automatically created or copied, therefore you have to configure field mapping for each newly connected Jira instance. For more information, go to [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918700586](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918700586)
2. **Scope definition** - when another Jira Cloud instance is added to the app, you can add it to a box scope in box configuration and define scope’s details:
> Macro (iframe)