🐰 New: Triage — a self-updating cross-repository queue that prioritizes pull requests by value and risk, so you always know what to review next. Now in beta! Explore Triage →
Turn code discussions into tracked issues across GitHub, GitLab, Jira, and Linear directly from CodeRabbit’s chat interface.
| When reviewing code, important issues often surface in discussions but get lost without proper tracking. CodeRabbit bridges this gap by creating issues directly from pull request conversations or chat interactions, ensuring nothing falls through the cracks.CodeRabbit supports issue creation across GitHub, GitLab, Jira, and Linear. You can create issues naturally through conversations—just mention @coderabbitai and describe what needs to be tracked.
The most straightforward way to create issues is through CodeRabbit’s chat interface. During pull request reviews or in comment threads, mention @coderabbitai and ask to create an issue. CodeRabbit analyzes the context and creates a well-structured issue with relevant details (code context, discussion history, etc.) for your chosen platform. For Jira, you can create a new issue or a sub-task for an existing issue.
Creating an issue through CodeRabbit's agentic chat interface
Include relevant code snippets, error messages, or discussion context when
requesting issue creation. This helps CodeRabbit generate more detailed and
actionable issues.
Specify the platform
If you have multiple issue platforms configured, explicitly mention which one to use: “Create a Jira ticket for this” or “Add this to Linear.”
Include assignee information
Mention specific team members who should handle the issue: “Create an issue
for @username to investigate this performance problem.”
Set priority and timing
Indicate urgency or deadlines: “Create a high-priority issue for the memory
leak in checkout flow” or “Add this to the next sprint.”
For detailed information about configuring issue tracking integrations, see our Issue Integrations guide.
