Issue Enrichment is a beta feature.
Overview
CodeRabbit Issue Enrichment automatically analyzes your issues and provides contextual
insights to help you work more efficiently. When you create or edit an issue, CodeRabbit
posts a comment with:
- 🔍 Duplicate Detection - Identifies if your issue already exists
- 🔗 Similar Issues - Shows related issues that might have solutions or context
- 🔗 Related Pull Requests - Finds PRs that addressed similar problems
- 👤 Suggested Assignees - Recommends team members based on expertise
- 🏷️ Smart Labeling - Automatically categorizes issues with appropriate labels
Looking to generate implementation plans from issues? Check out CodeRabbit
Plan Mode for comprehensive step-by-step guides. Getting Started
Issue enrichment is enabled by default on GitHub issues. CodeRabbit will automatically enrich new issues with contextual information.
Disable Issue Enrichment
To turn off automatic enrichment, add this to your .coderabbit.yaml configuration file:
issue_enrichment:
auto_enrich:
enabled: false
Features
Duplicate Detection
CodeRabbit analyzes your issue against existing issues in your repository and knowledge
base to detect potential duplicates.
What you’ll see:
## 🔗 Similar Issues
**Possible Duplicates**
- https://github.com/owner/repo/issues/42
Similar Issues
Discover related issues that might provide context, workarounds, or solutions.
What you’ll see:
## 🔗 Similar Issues
**Related Issues**
- https://github.com/owner/repo/issues/15
- https://github.com/owner/repo/issues/28
- https://github.com/owner/repo/issues/31
## 🔗 Related PRs
#123 - Fix authentication bug [merged]
#145 - Update auth flow [open]
#98 - Improve login error handling [closed]
Suggested Assignees
Get smart recommendations for who should work on the issue based on past contributions
to related issues and PRs.
What you’ll see:
## 👤 Suggested Assignees
- [@guritfaq](https://github.com/guritfaq)
- [@harjotgill](https://github.com/harjotgill)
- [@aravindputrevu](https://github.com/aravindputrevu)
Smart Auto-Labeling
Automatically apply appropriate labels to issues based on their content.
Configuration
issue_enrichment:
labeling:
auto_apply_labels: true
labeling_instructions:
- label: bug
instructions: Issues reporting bugs, errors, crashes, incorrect behavior, or unexpected results. This includes runtime errors, logic errors, broken functionality, regressions, and any deviation from expected or documented behavior.
- label: enhancement
instructions: Feature requests, improvements to existing functionality, performance optimizations, refactoring suggestions, UI/UX enhancements, and any suggestions to make the project better or add new capabilities.
- label: documentation
instructions: Documentation updates, additions, corrections, or clarifications needed. This includes missing docs, outdated information, unclear instructions, API documentation, code examples, README improvements, and any requests for better explanations or guides.
Currently Supported
- ✅ GitHub - Full support for all enrichment features
Coming Soon
- 🔄 Linear - Native Linear issue tracker enrichment
- 🔄 Jira - Native Jira issue tracker enrichment
Frequently Asked Questions
Currently, the enrichment format is standardized, but you can customize label categories with auto-labeling and configure auto-planning to choose which issues get plans.
Does enrichment work for private repositories?
Yes! Issue enrichment works for both public and private repositories. Knowledge base and
enrichment respect your repository access controls.
CodeRabbit uses semantic similarity search on your knowledge base by indexing issues and PRs based upon vectorized representations (which cannot be reversed into the original issues and PR’s).
Will enrichment update when I edit the issue?
Yes! When you edit an issue that already has enrichment, CodeRabbit will re-analyze the updated content, search for new related issues and PRs, update the enrichment comment, and trigger auto-planning if labels changed.
Support and Feedback
