← AI resource directoryenterprise-application-connectors

enterprise-application-connectors · prepared

Atlassian Jira Cloud REST API connector boundary

Official-source REST v3, OAuth 3LO, Forge/Connect, scope, user-permission, anonymous, read, and mutation boundaries for Jira connectors.

version 1.0.0freshness currentobserved 2026-08-27T01:30:00Z

resource.connector.atlassian-jira-cloud-rest-api
sha256:db4f0d035d3deb7cb9f70406549d4ddb0e7407847d87e83fe6f04b3792f0f4e3

Open canonical machine JSON →

Evidence-backed facts

  1. Jira REST v3 exposes programmatic resource operations, and each operation documents scopes, permissions, anonymous availability, pagination, and response behavior. informative
  2. A mutating operation requires both the API authorization mechanism and the calling user or app's Jira permissions for the target resource. informative
  3. Forge uses scopes, Connect uses JWT and scopes or impersonation, and other integrations are directed to OAuth 2.0 authorization-code grants; basic auth is for personal scripts. informative
  4. Anonymous access exists only where an operation explicitly declares it and underlying Jira permissions permit it; authentication never bypasses project or issue security. informative