Connect Confluence and Jira
Authorize one Atlassian connection and index Confluence pages and Jira issues per site.
One Atlassian connection covers both Confluence and Jira. Orcha reads authorized pages and issues with stable identifiers and direct citations, and never changes Atlassian content.
You need the workspace admin role in Orcha and access to the Atlassian site.
Add the connector
- Open Connectors and choose Confluence and Jira.
- Approve Atlassian's consent screen and grant the site (or sites) to share. Scopes are read-only.
- Orcha catalogs each site as two resources, one for Confluence pages and one for Jira issues, each with its own indexing policy.
Choose what gets indexed
Both resources start in Index names only mode. Confluence pages can be
retained per space or subtree. Jira issues follow a catalog-plus-live
model: issue inventory is browsable, retained issues are indexed, and
fresh search can also query Jira live for current state.
Use it
Indexed pages and issues come back from search cited to the exact page or issue key, with a link into Atlassian, from the Orcha app, the REST API, and AI assistants connected over MCP.
Remove it
- Pause stops syncing while keeping indexed content searchable.
- Revoke invalidates Orcha's Atlassian credential and deactivates the sites; indexed content is kept until you disconnect or reconnect.
- Disconnect purges indexed documents, search chunks, cached content, and sync state from your workspace.
- From Atlassian: remove Orcha under Connected apps in your Atlassian account. Then disconnect in Orcha to purge indexed content as well.