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.
Go to https://id.atlassian.com and sign in with your Atlassian account.
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
Once signed in, go to the API token management page: https://id.atlassian.com/manage/api-tokens
Click Create API token.
Enter a label (for example,
Asset Panda Integration) and click Create.Click Copy to clipboard and save the token in a secure location. You’ll need it when configuring the connection in Asset Panda.
This token serves as your secure login for Asset Panda. Keep it private and do not share it.
Find your Jira Site URL
Go to your Jira Service Management project.
Review the URL in your browser’s address bar.
Copy the base URL; for example:
https://yourcompany.atlassian.net
Asset Panda Pro tasks
Set up the Jira integration
Log into Asset Panda Pro with an administrator account
Navigate to
Settings > Account Management.Expand the appropriate account and module.
Click Manage in the Integrations card.
Select Integrations Store.
In the Jira tile, click Add. The Integrations in this module tab is displayed.
In the Jira tile, click Configure.
In the URL field, enter the Jira site URL you copied earlier (for example,
https://yourcompany.atlassian.net).In the API Token field, paste the token you generated.
Click Test and save connection to verify the credentials. If the connection is successful, a green check is displayed above the Authentication tab.
Once verified, click Continue with mapping.
Create Mapping
After authentication, the Mapping List screen will appear.
Click Add mapping option to begin.
Enter a Mapping Name that identifies the sync purpose (e.g.,
Jira Tickets → AP Support Items).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)
Select the Collection in Asset Panda Pro that should receive the records.
Select the Unique Identifier fields to be mapped between Jira and Asset Panda Pro. See Unique identifiers.
Set Sync Direction to Push to Asset Panda.
If necessary, click to apply filters to limit synced data (for example, only tickets from certain projects or issue types).
To map additional fields, click Add more and then select the field mappings. See Field mapping and identifier reference.
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.
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.
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
Last updated