Skip to content

Troubleshooting

  1. Verify JIRA_CLIENT_ID and JIRA_CLIENT_SECRET are correctly set in Settings
  2. Confirm the OAuth 2.0 integration is active in developer.atlassian.com
  3. Check that read:jira-work and read:jira-user scopes are configured in your Atlassian app
  4. Review server logs for specific error messages from the token endpoint
  1. Verify the OAuth integration has been consented to by an organization admin
  2. Check that your Atlassian account has access to at least one Jira Cloud instance
  3. Manually set JIRA_CLOUD_ID in the Admin UI — you can find it in the Atlassian developer console under your app’s authorization details
  1. Verify the Jira agent is enabled on Settings → Agents in the Admin UI
  2. Try specifying a project explicitly (e.g., “search PROJ project for login bugs”)
  3. Check that your OAuth scopes include read:jira-work
  4. Try simpler queries — the query enhancer works best with descriptive natural language
  1. Verify Jira is enabled on the Sources page in the Admin UI
  2. Confirm at least one project key is configured
  3. Check that RQ workers are running: docker-compose ps rq-worker-1
  4. Check the RQ Dashboard at http://localhost:9181 for failed jobs
  5. Trigger extraction manually via the Sources page
  1. Verify the Jira agent is enabled on Settings → Agents in the Admin UI
  2. Confirm both JIRA_CLIENT_ID and JIRA_CLIENT_SECRET are set
  3. Check the Health page for Jira connection status
  4. Try the manual override: prefix your query with /jira