Integrations
Jira + Asset Panda Pro
Connect Jira Service Management tickets with the assets behind them. Import mapped records and send supported ticket updates back through automation.
Key benefits
-
Give agents asset context without switching tabs
Use the Asset Panda Pro app for Jira to search for and link assets while reviewing a service ticket.
-
Keep relevant issue details together
Map Jira issue information into an Asset Panda Pro collection using identifiers and fields that support your service workflow.
-
Reduce repetitive ticket updates
Use an Asset Panda Pro automation to send supported changes in ticket status, ownership, and other mapped fields back to Jira.
What Jira data and workflows are supported?
Jira-to-Asset Panda mapping and updates sent back to Jira are configured separately.
| Record / workflow | Direction | What it supports |
|---|---|---|
| Jira tickets and issues | Jira to Asset Panda Pro | Import mapped issue fields, including Issue ID, Summary, Description, Status, Priority, Assignee, Reporter, and project information. |
| Jira asset records | Jira to Asset Panda Pro | Map Jira asset records to a selected Asset Panda Pro collection using compatible fields and unique identifiers. |
| Selected ticket updates | Asset Panda Pro to Jira | An enabled automation can update Priority, Assignee, Status, Summary, and Reporter in Jira. |
| Asset-to-ticket linking | Within Jira Cloud | Find and associate Asset Panda Pro assets with Jira tickets through the Asset Panda Pro Jira app. |
Outbound updates are limited to supported Jira ticket fields: Priority, Assignee, Status, Summary, and Reporter. General asset data is not pushed from Asset Panda Pro to Jira.
How the Jira integration works
-
Connect your Jira account
Create an Atlassian API token. Add Jira from the Asset Panda Pro Integrations Store, enter your Jira site URL and token, then test and save the connection.
-
Map your Jira records
Select the Jira record type and destination collection. Match unique identifiers and relevant fields, with optional filters for specific projects or issue types.
-
Configure ticket updates
To send changes back to Jira, enable an automation triggered by updated records and map the supported fields for the "Update ticket(s) to Jira" action.
-
Link assets while working in Jira
Install the Asset Panda Pro app from the Atlassian Marketplace to search for and link assets directly within Jira. This is a separate step from connecting Jira through the Asset Panda Pro Integrations Store.
Detailed setup: Jira Integration Knowledge Base
Requirements
- An active Asset Panda Pro subscription with administrator access.
- Administrator permissions for Jira and the connected Atlassian account.
- Your Jira Service Management site URL and an Atlassian API token.
- A destination Asset Panda Pro collection for mapped Jira records.
- To link assets directly within Jira, install the Asset Panda Pro app from the Atlassian Marketplace. This installation is separate from the Jira connection configured in the Asset Panda Pro Integrations Store.
Frequently asked questions
Does Asset Panda Pro integrate with Jira Service Management?
Yes. You can map Jira service tickets and supported asset records into Asset Panda Pro, associate assets with Jira issues, and configure selected ticket updates back to Jira.
Which Jira ticket fields can I import?
Supported mappings include Issue ID, Summary, Description, Issue Type, Status, Priority, Reporter, Assignee, Project, dates, labels, linked Asset ID, and compatible custom fields.
Can Asset Panda Pro send ticket changes back to Jira?
Yes. Use the "Update ticket(s) to Jira" automation to update supported ticket fields, including Priority, Assignee, Status, Summary, and Reporter. The integration does not push general asset data from Asset Panda Pro to Jira.
Can I link assets to tickets without leaving Jira?
Yes. With the Asset Panda Pro app for Jira installed, you can search for and link Asset Panda Pro assets directly to Jira tickets without switching between platforms.
Can I limit which Jira records are imported?
Yes. Apply mapping filters to include tickets from selected projects or issue types.
How does the integration avoid duplicate records?
Use stable, unique identifiers in the mapping, such as Jira Issue ID and a unique field in the destination Asset Panda Pro collection, to match records during updates.
What do I need to set up the Jira connection?
You need an active Asset Panda Pro subscription, administrator permissions in Asset Panda Pro and Jira/Atlassian, your Jira site URL, and an Atlassian API token.
About Jira Service Management
Jira Service Management is Atlassian's platform for organizing service requests and tracking issues across IT and other service teams. Connecting it with Asset Panda Pro helps teams relate that service work to the assets involved.
Connect service tickets with asset visibility
Give technicians clearer asset context and keep supported ticket information connected across your service desk and asset records.