Jira Integration

The Jira Service Management integration with Asset Panda 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.

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.

Important: You must be an administrator in both Jira and Atlassian to complete the setup steps below

Jira Tasks

Sign in with Atlassian

1. Go to 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: 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.

Note: This token serves as your secure login for Asset Panda. Keep it private and do not share it.

---

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

---

Asset Panda Tasks

Setup Jira in Asset Panda

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.

Info: A green checkmark above the Authentication tab confirms a successful connection.

---

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)

1. Select the Collection in Asset Panda that should receive the records.

2. Set Sync Direction to Push to Asset Panda.

3. (Optional) Apply filters to limit synced data (e.g., only tickets from certain projects or issue types).

---

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.

---

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.