Jira
Jira Cloud, Jira Data Center, Jira Server.
Access mode: Read-only
Required information
| Field | Details |
|---|---|
| Instance URL | Cloud: https://<org>.atlassian.net. Data Center: self-hosted URL. |
| Project key(s) | Jira projects to access (e.g., DATA, ENG, INFRA). |
| Authentication | Cloud: API token + email or OAuth 2.0 app. Data Center: PAT. |
| API permissions | Read-only: read:jira-work, read:jira-user. |
Network considerations
Cloud: HTTPS to <org>.atlassian.net. No VPN needed.
Data Center: VPN or reverse proxy. REST API at /rest/api/2/ or /rest/api/3/.
Atlassian Access: If org uses IP allowlisting, add Flume’s IPs.
Credential and auth management
Preferred (Cloud): OAuth 2.0 (3LO) app. Registered in Atlassian Developer Console. Granular scopes. Token refresh automatic.
Acceptable (Cloud): API token. Per-user at id.atlassian.com. Basic auth (email:token).
Data Center: PAT. User-scoped.
Rate limits: Cloud has rate limits. Flume respects Retry-After.
Validation checks
| Check | Method | Expected result |
|---|---|---|
| Authentication | GET /rest/api/3/myself | Returns authenticated user |
| Project access | GET /rest/api/3/project/<key> | Returns project details |
| Issue search | POST /rest/api/3/search with JQL: project = <key> ORDER BY updated DESC | Returns issues |
| Issue detail | GET /rest/api/3/issue/<key>-1?expand=changelog | Returns full issue with history |
Every connection starts from the pre-engagement checklist and goes through the universal validation protocol before production sign-off.