Connect Confluence and Jira
Authorize one Atlassian connection and index Confluence pages and Jira issues for each site.
One Atlassian connection gives access to Confluence and Jira. Orcha reads the pages and issues that you authorize. Each item has a stable identifier and a direct citation. Orcha does not change Atlassian content.
You must have the workspace admin role in Orcha. You must also have access to the Atlassian site.
Add the connector
- Open Connectors.
- Select Confluence and Jira.
- Approve the Atlassian consent screen.
- Select the site or sites to share. The scopes are read-only.
Orcha catalogs each site as two resources. One resource contains the Confluence pages. The other resource contains the Jira issues. Each resource has its own indexing policy.
Choose what gets indexed
Both resources start in Index names only mode. You can keep Confluence pages for each space or subtree.
Jira issues use a catalog-plus-live model:
- You can browse the issue inventory.
- Orcha indexes the issues that you keep.
- A
freshsearch can also query Jira live for the current state.
Use it
Search returns indexed pages and issues. Each result cites the exact page or issue key and has a link to Atlassian. You can search from the Orcha app, the REST API, and AI assistants that connect over MCP.
Remove it
- Pause stops the sync. You can still search the indexed content.
- Revoke cancels the Orcha credential for Atlassian and deactivates the sites. Orcha keeps the indexed content until you disconnect or reconnect.
- Disconnect deletes the 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 also delete the indexed content.