# Jira Integration

Asset Panda integrates with Jira Service Management using either a direct API-based connection or the Asset Panda Pro app available on the Atlassian Marketplace. Both options enable teams to associate assets with support tickets, improve workflows, and maintain accurate asset visibility within Jira.

To integrate Jira Service Management with Asset Panda, you must first collect your Jira site URL and generate an API token. These credentials allow Asset Panda to authenticate and securely connect with your Jira account.

{% hint style="info" %}
***Important:** You must be an administrator in both Jira and Atlassian to complete the setup steps below*
{% endhint %}

## Integration Options <a href="#add-a-new-account" id="add-a-new-account"></a>

Asset Panda offers two methods to integrate with Jira Service Management:

1. Asset Panda Pro App (Jira Marketplace)
2. API-Based Integration (Configured within Asset Panda)

Choose the method or methods that best fits your workflow requirements.

## Option 1: Asset Panda Pro App (Jira Marketplace) <a href="#add-a-new-account" id="add-a-new-account"></a>

The Asset Panda Pro app allows users to access Asset Panda directly within Jira tickets. This enables users to search, view, and link asset records without leaving Jira.

Key Capabilities:

* Access Asset Panda inside Jira tickets
* Search and view asset records
* Link one or multiple assets to a ticket
* Open asset records in Asset Panda
* View linked Jira tickets inside Asset Panda (bi-directional visibility)

Installation Steps:

1. Go to the Atlassian Marketplace
2. Search for “Asset Panda Pro”
3. Click Get it now or Install
4. Select your Jira site
5. Complete installation

{% hint style="info" %}
***Important:*** Jira admin access is required to install the app. Non-admin users will need approval.
{% endhint %}

Using the App in Jira:

1. Open any Jira ticket
2. Click on “View app actions”
3. Select “Asset Panda Pro”
4. Log in to your Asset Panda account
5. Select account, module, and collection
6. Search and select asset records
7. Click “Link to Ticket” to associate assets

Additional Notes:

* Multiple assets can be linked to a single ticket
* Linked tickets are visible inside Asset Panda under the Tickets tab

***

## Option 2: API-Based Integration (Asset Panda Setup) <a href="#add-a-new-account" id="add-a-new-account"></a>

{% hint style="info" %}
***Important:*** The following steps apply to the API-based integration method.
{% endhint %}

### Sign in with Atlassian  <a href="#sign-in" id="sign-in"></a>

1. Go to [https://id.atlassian.com](https://id.atlassian.com/) and sign in with your Atlassian account.
2. Confirm that the account you’re using has the necessary admin permissions to access Jira Service Management and generate API tokens.&#x20;

***

### Generate your API Token <a href="#api-token" id="api-token"></a>

1. Once signed in, go to the API token management page: <https://id.atlassian.com/manage/api-tokens>
2. Click **Create API token**.
3. Enter a label (for example, *Asset Panda Integration*) and click **Create**.
4. Click **Copy to clipboard** and save the token in a secure location. You’ll need it when configuring the connection in Asset Panda.

{% hint style="info" %}
***Note:** This token serves as your secure login for Asset Panda. Keep it private and do not share it.*
{% endhint %}

***

### Find your Jira Site URL

1. Go to your Jira Service Management project.
2. Look at the URL in your browser’s address bar.
3. Copy the base URL, which typically looks like:\
   \
   `https://yourcompany.atlassian.net`

&#x20;

***

## Asset Panda Tasks&#x20;

### Setup Jira in Asset Panda <a href="#setup" id="setup"></a>

1. Log in to **Asset Panda**.
2. Navigate to **Settings** > **Account Management**.
3. Under the appropriate module, click **Manage** under **Integrations**.
4. Open the **Integrations Store** for the desired account.
5. In the Integration Store, find the **Jira** tile and click **Add**.
6. Switch to the **Integrations in this module** tab.
7. Locate the **Jira** tile and click **Configure**.
8. In the **URL** field, enter the Jira site URL you copied earlier (e.g., `https://yourcompany.atlassian.net`).
9. In the **API Token** field, paste the token you generated.
10. Click **Test and save connection** to verify the credentials.
11. Once verified, click **Continue with mapping** to proceed.

{% hint style="info" %}
&#x20;***Info**: A green checkmark above the **Authentication** tab confirms a successful connection.*
{% endhint %}

***

### Create Mapping

After authentication, the **Mapping List** screen will appear.

1. Click **Add mapping option** to begin.
2. Enter a **Mapping Name** that identifies the sync purpose (e.g., `Jira Tickets → AP Support Items`).
3. From the **External Entity** dropdown, select the data type to sync from Jira.

| External Entity | Description                                    |
| --------------- | ---------------------------------------------- |
| Ticket          | Jira issues/tickets created by users or agents |
| Asset           | Asset records managed or linked inside Jira    |
| Project         | Jira project metadata (limited cases)          |

4. Select the **Collection** in Asset Panda that should receive the records.
5. Set **Sync Direction** to **Push to Asset Panda**.
6. *(Optional)* Apply filters to limit synced data (e.g., only tickets from certain projects or issue types).

&#x20;

***

#### **Unique Identifier Table**

The unique identifier ensures that records in Jira are matched correctly with records in Asset Panda, avoiding duplication and ensuring updates are applied accurately.

| Platform    | Recommended Unique Identifier |
| ----------- | ----------------------------- |
| Jira        | Issue ID or Asset ID          |
| Asset Panda | Asset Tag (must be unique)    |

Use a stable and unique field such as **Issue ID** from Jira and **Asset Tag** in Asset Panda.&#x20;

***

#### **Mapping Table and Identifier Reference**

Use the field mapping section to connect fields between Jira and Asset Panda. Map fields with compatible data types to ensure sync accuracy.

| Field Name           | Description                                      | Mapping Guidance                           |
| -------------------- | ------------------------------------------------ | ------------------------------------------ |
| Issue ID             | Unique identifier for the Jira ticket or issue   | Recommended for unique ID if consistent    |
| Summary              | Short description of the ticket                  | Map for quick identification               |
| Description          | Full text content of the issue                   | Map for detailed notes or comments         |
| Issue Type           | Type of issue (e.g., Bug, Task, Service Request) | Map to categorize ticket types             |
| Status               | Current workflow state (e.g., Open, In Progress) | Map for workflow tracking                  |
| Priority             | Importance level of the issue                    | Map for SLA or escalation tracking         |
| Reporter             | User who submitted the ticket                    | Map for user reference                     |
| Assignee             | Agent assigned to resolve the ticket             | Map for ownership tracking                 |
| Project              | Project associated with the ticket               | Map to helpdesk team or department         |
| Created Date         | Date the ticket was created                      | Map for SLA or reporting                   |
| Updated Date         | Date of last modification                        | Map for monitoring activity                |
| Due Date             | Deadline for ticket resolution                   | Map for SLA compliance                     |
| Labels               | Tags or custom labels used for classification    | Map for filtering or tagging workflows     |
| Asset ID (if linked) | Identifier for linked asset record               | Map to Asset Tag in Asset Panda            |
| Custom Fields        | Any additional fields configured in Jira         | Map if used in workflows or internal logic |

Once your field mapping is complete, click **Save** to activate the integration.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://prohelp.assetpanda.com/integrations-store/ticket-management/jira-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.