Jira integration: API scope/permission issue (from Slack thread C04DRG7DGP2)

[harshithmullapudi]

Context

Reported in Slack thread: https://slack.com/archives/C04DRG7DGP2/p1774039520295959 (thread_ts: 1774039520.295959).

A Jira integration issue was reported, likely related to missing/incorrect API scopes or permissions during auth / API calls.

What we know

• Area: jira integration
• Symptom: API scope/permission issue (exact failure unknown)
• Source: Slack thread linked above

What’s missing

We don’t yet have enough details to determine whether this is:

• incorrect OAuth scope request
• missing Atlassian app permissions
• wrong Jira Cloud endpoint / product context
• token exchange/storage issue
• tenant/site mismatch

Request (please fill in)

• Jira deployment: Cloud / Server / Data Center
• Auth method used: OAuth 2.0 (3LO) / PAT / basic / other
• Exact CORE flow used (UI path / API route)
• Repro steps (start → expected → actual)
• Jira endpoints being called (full URL paths)
• Required scopes expected vs scopes currently requested
• Error message(s) + HTTP status code(s)
• Response body (sanitized)
• Relevant CORE logs (request id / timestamps)
• Tenant/site details (sanitized): cloudId / site URL

Notes

Tagging as integration issue for triage; once repro is known, we can map to the exact scope set and fix the auth/app config and/or API calls accordingly.