> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/integrations-store/ticket-management/jira-integration.md).
# Jira Integration
The Jira Service Management integration with Asset Panda Pro enables seamless synchronization of asset data between your service desk and asset inventory. By connecting the two platforms, you can associate assets with support tickets, improve issue resolution workflows, and maintain accurate asset visibility within Jira.
## Prerequisites
* Active Asset Panda Pro subscription with Administrator access
* Administrator permissions in Jira and Atlassian
***
## Jira tasks
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 Pro to authenticate and securely connect with your Jira account.
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.
### Generate your API Token
1. Once signed in, go to the API token management page:
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="warning" %}
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. Review the URL in your browser’s address bar.
3. Copy the base URL; for example: `https://yourcompany.atlassian.net`
***
## Asset Panda Pro tasks
### Set up the Jira integration
1. Log into Asset Panda Pro with an administrator account
2. Navigate to **Settings** > **Account Management**.
3. Expand the appropriate account and module.
4. Click **Manage** in the **Integrations** card.
5. In the **Jira** tile, click **Add**, and then click **Edit**.
6. In the **URL** field, enter the Jira site URL you copied earlier (for example, `https://yourcompany.atlassian.net`).
7. In the **API Token** field, paste the token you generated.
8. Click **Test and save connection** to verify the credentials. If the connection is successful, a green check is displayed above the **Authentication** tab.
9. Once verified, click **Continue with mapping**.
***
### 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. For **External Entity**, select the data type to sync from Jira:
* **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 Pro that should receive the records.
5. Select the **Unique Identifier** fields to be mapped between Jira and Asset Panda Pro. See [Unique identifiers](#mapping-table).
6. Set **Sync Direction** to **Push to Asset Panda**.
7. If necessary, click :filter: to apply filters to limit synced data (for example, only tickets from certain projects or issue types).
8. To map additional fields, click **Add more** and then select the field mappings. See [Field mapping and identifier reference](#field-mapping-table).
9. Click **Save**.
***
#### **Unique identifiers**
The unique identifier ensures that records in Jira are matched correctly with records in Asset Panda to avoid duplication and ensure updates are applied accurately. For example, you should use a stable and unique field, such as **Issue ID** in Jira and **Asset Tag** in Asset Panda.
Platform
Recommended Unique Identifier
Jira
Issue ID or Asset ID
Asset Panda
Asset Tag (must be unique)
#### **Field mapping and identifier reference**
Use the field mapping section to connect fields between Jira and Asset Panda Pro. 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 |
### Two-way sync: Sending updates back to Jira
While the Mapping List page handles inbound sync of Jira tickets into Asset Panda Pro, updates made in Asset Panda Pro can be pushed back to Jira using an **Automation**.
#### Set up the automation
1. Navigate to **Automation** from **Account Management**.
2. Click to create a new automation.
#### Trigger
1. Set **Trigger** to **When a record is updated**.
2. Under **By**, select the applicable options (*Manual, Import, API, Form, Automation*) - or **Include all options**.
3. Under **Using**, select the same **Collection** that receives the inbound Jira sync (the collection configured in *Create Mapping from integration page*).
#### Action
1. Set **Type** to **Update ticket(s) to Jira**.
2. Under **Field Mapping**, click **Create**.
#### Map fields
1. In the Field Mapping screen, the **Jira id → ID** row is pre-set and identifies the ticket to update.
2. For each additional field to sync back, select the **Asset Panda Pro** field on the left and the corresponding **Jira** field on the right.
3. Supported Jira fields for outbound updates:
* Priority
* Assignee
* Status
* Summary
* Reporter
4. Click **Add** to map additional fields as needed.
5. Click **Save**.
Add **Match** conditions if the automation should only fire for certain records (e.g. specific Collection filters), then click **Add Condition** as needed.
#### Enable the automation
1. Name the automation (e.g. *Send ticket updates to Jira*).
2. Toggle the automation to **Enabled**.