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