---
title: "Connect Jira cloud instance"
canonical: "https://support.appfire.com/space/SPM/1918700300/Connect%20Jira%20cloud%20instance"
format: markdown
---
| **Contents:**<br>> Macro (toc) |
| --- |

## Overview

To use additional Jira Clouds, you need to:

- **connect them to the app **(you can do it in App Configuration or directly in one of the boxes)
- **add them to the scope of your boxes**

## Before you proceed

### WebHooks

> ℹ️ Make sure to register [https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918506277](https://appfire.atlassian.net/wiki/spaces/SPM/pages/1918506277).
> ℹ️ 
> ℹ️ WebHook setup is necessary for automatic synchronization between the primary and a secondary Jira Cloud.

### App

The app must be installed on must be installed on the primary and secondary Jira Cloud instances. 

If someone else is setting up the additional Jira Cloud connection, provide them with the [token](https://id.atlassian.com/manage-profile/security/api-tokens).

### Required fields information

To set up a connection, you will need:

- [API token](https://id.atlassian.com/manage-profile/security/api-tokens) (must be generated from the technical user account)
- Fill in the information and click next:
- Provide the app’s endpoint URL and check the boxes:
- Click "**Connect**".

## Result - box scope

1. Add new integration.
2. Open the selection dropdown.
3. Select "**Jira Cloud**" from the list.
4. Open the "Connection" dropdown and select the Jira Cloud connection.
5. Click "Add".

Data from the additional Jira Cloud can be added to the scope. 

![image](media://ac128209-7516-4cd9-a6e7-be44acff292b)

After Jira Cloud is connected, the following features are available:

- Scope definition - you can base the scope on Jira Cloud projects from the additional connection
- You can add the fields from connected Jira Clouds to column views/card views
- You can define the structure builders for the additional Jira Cloud connections
- Field mapping of the connected Jira Clouds can be managed in App Configuration
- Dependencies mapping of connected Jira Clouds can be set in App Configuration

![image](media://064403bc-adf7-47be-967f-b14d260b5a38)

**Additional requirements:**

The app works properly when connected to Jira Cloud is valid.

## Constraints

- **Task creation** → You can't use the app to create tasks in the additional Jira Cloud. When you add tasks, they are added to the primary Jira.
- **Task grouping** (using the "status" field): → tasks from two different Jiras can't be grouped into unified groups.
- **Task report **→ doesn't allow using Jira fields from the additional Jira Cloud.

## Additional configuration

**Field mapping and dependency mapping of the newly connected Jira Cloud are empty and need to be set up.**

You can use the matching app fields of the secondary Jira Cloud or different fields for mapping. The only requirement is that you create a mapping.

**All fields you want to use for mapping must be added to your Jira projects**. Otherwise, the app won't be able to update them.

- You can't use the 'not synchronized' option for the secondary Jira Cloud
- The app fields are not automatically added to the secondary Jira Cloud screens

### App custom fields

Are you using custom fields created by the app? You can use matching fields for the secondary Jira Cloud.

Additional custom fields were created on the Jira instance during the app installation. You can find them in the Jira Settings of the primary instance ("Custom fields").

![image](media://daf38e74-a509-4621-83ce-4053068dbd3d)

### Dependencies

Link types can be found, added, and configured in the 'issue linking' section of Jira administration.

![image2022-7-13_10-30-36.png](media://0c41aadb-83f4-4908-a0a1-1e15e4b80f29)