Documentation Index Fetch the complete documentation index at: https://docs.parable.work/llms.txt
Use this file to discover all available pages before exploring further.
What You'll Need Credential Description Username Jira account username Personal Access Token Generated from Jira profile Base URL Your Jira Server URL
Overview Personal Access Tokens (PATs) provide secure, token-based authentication for Jira Server and Data Center without exposing passwords. Prerequisites Administrator access required. You need privileges in to complete this setup.If you don’t have admin access, contact your administrator to:
Create the API credentials on your behalf, OR
Grant you temporary admin access to complete the setup
Jira Administrator or user with Browse Projects permissionPersonal Access Tokens enabled on your instance (Jira 8.14+)
Network access to your Jira Server
Setup Guide
Access Profile Settings
Log in to your Jira Server instance
Click your avatar → Profile
Navigate to Personal Access Tokens
PATs require Jira Server 8.14 or later. For older versions, use Basic Auth with username/password.
Create Personal Access Token
Click Create token
Enter name: Parable Integration
Set expiration (optional)
Click Create
Copy your now! This is the only time it will be displayed. Store it in a secure password manager before closing this page.
Note Your Base URL
Your Jira Server URL format: https://jira.yourcompany.com
Verify Your Setup With Personal Access Token
With Basic Auth (older versions)
curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://jira.yourcompany.com/rest/api/2/myself"
Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now proceed to configure this connector in Parable.
API Differences from Cloud Feature Jira Server Jira Cloud API Version v2 v2 and v3 Auth PAT or Basic API Token + Basic Base URL Custom *.atlassian.netAudit Logs Limited Full
Rate Limits: enforces rate limits of .Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.
Troubleshooting Error Meaning Solution 401 UnauthorizedInvalid credentials Verify username and token/password 403 ForbiddenNo permission Check user has required permissions Connection refusedNetwork issue Verify server URL and network access
PATs not available Personal Access Tokens require Jira 8.14+. For older versions, use Basic Authentication. SSL certificate errors Self-signed certificates may cause issues. Ensure proper certificate configuration. Additional Resources
Jira Server REST API Official API documentation
