The Jira connector synchronizes issues from a Jira project using the Jira REST API v3.
Authentication
OAuth — requires scopes:
read:jira-workoffline_access
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Jira Domain | Input | Yes | e.g., yoursite.atlassian.net |
| Project | Selector / Input | Yes | Project key |
| JQL Filter | Input | No | Custom JQL to filter issues |
| Max Issues | Input | No | Limit the number of synced issues |
How It Works
- Cloud ID Resolution — Resolves Atlassian cloud ID from domain
- JQL Construction — Builds
project = "KEY" ORDER BY updated DESCwith optional custom JQL filter - Issue Search — Uses Jira REST API v3 search endpoint
- ADF Extraction — Converts Atlassian Document Format in descriptions and comments to plain text
- Pagination —
startAt/maxResultsoffset pagination
Document Format
KEY-123: Issue summary
Description text...
Comment text 1...
Comment text 2...Metadata Tags
| Tag | Type | Description |
|---|---|---|
| Issue Type | Text | Bug, Story, Task, etc. |
| Status | Text | Current workflow status |
| Priority | Text | Issue priority level |
| Labels | Text | Comma-separated labels |
| Assignee | Text | Assigned person |
| Last Updated | Date | When the issue was last updated |
JQL Validation
Custom JQL filters are validated during setup. Invalid JQL returns an immediate error.