Jira uses Member accounts. Each person connects their own Jira Cloud account, and Search calls Jira with that person's OAuth grant. There is no Jira service-account mode or admin project filter in live Search.
Set up Jira
- An organization admin opens Settings → Sources → Add source → Jira and adds it.
- Each teammate opens Integrations → Jira → Connect and authorizes their own Atlassian account.
- Search for a known issue or ask the assistant a question about it. There is no project-setup or indexing step after authorization.
Hosted Sim supplies the OAuth app. Self-hosted deployments must configure the app below. Use Jira Cloud; Jira Server and Data Center are not supported by this live adapter.
What Search does
Sim resolves the connected account's accessible Atlassian sites, sends JQL to Jira's search API, and returns issue summaries and descriptions. Reading a result fetches the issue and the comments returned by Jira with the same account. Jira enforces project permissions, issue security, and app-access restrictions on these requests.
The assistant can use JQL to narrow a question to a project, status, date, or other supported field. This is a per-query filter, not an organization source configuration. Search checks up to four accessible sites by default. A native query can select a specific cloud site ID and follow its continuation cursor.
Changes become visible when Jira's own search reflects them. Sim does not crawl issue attachments or retain an indexed copy of issue content. Bounded API responses may omit additional comments; open the source for the full issue.
Troubleshooting
| Problem | What to check |
|---|---|
| Jira is missing | Ask an organization admin to add Jira in Sources. |
| Connected, but no issue | Open it with the connected Jira account; check issue security, project permissions, site selection, and the JQL query. |
| Project is visible but its issues are unavailable | Check Atlassian app-access or data-security restrictions. Seeing a project does not guarantee the app can read its issues. |
| Reconnect | Authorize the appropriate account and grant the requested scopes. |
| OAuth popup does not open | Allow popups for Sim and retry Connect. |
| Invalid callback | Check the deployment OAuth app and exact scheme, host, port, and callback path. |
Search does not edit issues. Sim's shared account connection may request additional permissions for workflow actions.
Self-hosted operator setup
Configure one shared Jira OAuth app for the deployment:
- In the Atlassian developer console, select or create an OAuth 2.0 integration.
- Under Authorization → OAuth 2.0 (3LO), add
https://<your-sim-domain>/api/auth/oauth2/callback/jiraas a callback. - Under Permissions, add Jira API and configure the full
jirascope list from Sim's OAuth configuration, including its Jira Service Management and Assets scopes. Add User Identity API → read:me. Sim requestsoffline_accessfor refresh tokens; Search uses only read operations, but this shared app also supports workflow actions. - Enable sharing under Distribution. Set
JIRA_CLIENT_IDandJIRA_CLIENT_SECRETfrom the app's Settings, verifyNEXT_PUBLIC_APP_URL, and restart Sim. - Connect from Integrations and select the configured site. After changing the OAuth client or requested scopes, update the organization’s provider configuration and have affected teammates reconnect.
The callback must match Sim's scheme, hostname, port, and path exactly. If only the app owner can connect, check Distribution. See the Atlassian OAuth guide and Sim deployment reference.