PSA Data Export guide
Create Jira Service Management API credentials for backup
Set up least-privilege Jira Service Management read access using Atlassian OAuth/API token or Data Center credentials, with tenant and regional details checked before backup.
On this page
Before you create credentials
Sign in as an administrator authorized to create integrations. Decide who owns rotation and revocation. Confirm the account plan exposes the modules you need and use a dedicated integration identity rather than a person's everyday login.
Create the Jira Service Management credential
For Cloud, create a scoped token/OAuth app and capture the site; for Data Center, use the instance's supported authentication and version-specific REST base. The current native model is Atlassian OAuth/API token or Data Center credentials. Follow the Jira Service Management official documentation in the live tenant because labels, available scopes, and regional hosts can change.
Choose read access
Request read access only for requests and issue fields, comments and worklogs, organizations and participants, and attachment metadata and files. Do not grant create, update, or delete permissions when the vendor offers separate scopes. Some products attach visibility to the underlying user role even when a token itself exists.
Record connection details safely
Keep the credential secret together with the tenant identifier, subdomain or base URL, region/data center, expiration date, and granted scopes. Do not paste secrets into tickets, screenshots, source control, browser localStorage, or this marketing site.
Validate the connection
Call a harmless documented read endpoint, confirm the expected tenant, then list a small sample from each selected record group. Record permission failures and unavailable modules. Choose Cloud or Data Center instructions first. Cloud JSM request APIs and Data Center Jira REST endpoints are related but not interchangeable.
Rotate or revoke access
Create the replacement first, validate it, update the consuming application through its secret store, then revoke the prior credential. Recheck scheduled captures after a role, license, region, or owner changes.
Plan your independent PSA archive
Keep source history available after your move. Join the waitlist for invitation-only BackupPSA access, or contact us about your platform.