The Jira source connector documentation and reference materials provided only describe authentication via Jira API token, email, and domain, and do not mention any required or recommended OAuth scopes for that token. They also do not differentiate behavior between “no scopes” and “full read scopes,” nor list a minimal scope set for the connector to function correctly.[[Jira source](
https://docs.airbyte.com/integrations/sources/jira)] Because of this, I’m sorry, but the knowledge sources do not contain enough information to say which specific Jira scopes are required or incompatible when using scoped tokens. Given this limitation, your best options are: 1. Use the unscoped API token as described in the Jira connector docs, since that is the documented and supported path.[[Jira source](
https://docs.airbyte.com/integrations/sources/jira)] 2. If you need to restrict scopes for security/compliance, I recommend: - Testing a minimally scoped token incrementally against the streams you actually use (see the supported streams list).[[Jira streams](
https://docs.airbyte.com/integrations/sources/jira#supported-streams)] - If a particular scope configuration causes failures, capture the exact error and open a discussion/issue as suggested in the troubleshooting section so the Airbyte team can confirm supported scope sets.[[Jira troubleshooting](
https://docs.airbyte.com/integrations/sources/jira#troubleshooting)] If you can share the exact error message you see with “full read” scopes, I can help you interpret it against the existing Jira connector docs.