> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coderabbit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Triage new engineering tickets

> Set up a CodeRabbit automation that investigates each new Linear, Jira, or GitHub issue against your code and posts the likely cause and a suggested fix on the issue or in a Slack channel.

Cloud Only (This feature is available on CodeRabbit Cloud only. It is not available on self-hosted CodeRabbit deployments.)

## What you get

When a Linear, Jira, or GitHub issue is created, CodeRabbit investigates it against your code. Pick the route by where the result should go:

| Result | Template |
| - | - |
| A comment on the issue with the problem summary, the likely cause, and a suggested fix with implementation steps and tests | **Recommend fix on Linear issue**, **Recommend fix on Jira issue**, or **Recommend fix on GitHub issue** |
| A problem summary and fix proposal in a Slack or Discord channel | **Triage Linear issue**, **Triage Jira issue**, or **Triage GitHub issue** |
| A summary, the affected area, related work, and a suggested owner, priority, and effort for issues posted in a Slack channel | `/automations` with the **Triage engineering issues** purpose |

None of these templates change issue fields or open a pull request.

## Before you start

| Requirement | Who does it | Where |
| - | - | - |
| Linear or Jira connected, or the CodeRabbit GitHub App installed for GitHub issues | A CodeRabbit admin; a GitHub organization owner for the app | [Connections](https://docs.coderabbit.ai/connections.md), or GitHub |
| The tracker connection and your repositories in the run's scope | A CodeRabbit admin | [Base Scope](https://docs.coderabbit.ai/automations/destinations.md#connections-and-base-scope), or **Slack** > **Channel mappings** for automations that post to Slack |
| Agent billing: the Automations Agent trial or paid Agent access for comments on the issue, CodeRabbit Agent for Slack or Discord for channel results. See [Who can use Automations](https://docs.coderabbit.ai/automations.md#who-can-use-automations). | A CodeRabbit admin | **Automations Agent usage** card on the Automations page, or **Billing** |

CodeRabbit manages the webhooks for Linear and Jira, and GitHub triggers use the CodeRabbit GitHub App, so there is nothing to set up in the tracker.

## Set it up

### Comment on the issue

**1. Open the template**

Open **Automations** > **Home** and select **Investigate tickets** under **Templates**. On the **Investigate new tickets** card, under **Choose your ticketing system**, choose **Linear**, **Jira**, or **GitHub Issues**, and select **Set up**. The editor opens with the **Recommend fix on Linear issue**, **Recommend fix on Jira issue**, or **Recommend fix on GitHub issue** template.

**2. Choose what to watch**

In the **Trigger** card, choose the connection and narrow it: **Linear teams** for Linear, **Jira projects** for Jira, or the **Repository** for GitHub. See [Managed webhooks](https://docs.coderabbit.ai/automations/triggers.md#managed-webhooks).

**3. Choose where the comment goes**

In the **Target** card, choose the Linear or Jira connection, or the GitHub repository, that writes the comment.

**4. Save**

Set the toggle to **Active** and select **Save automation**.

### Post to a Slack or Discord channel

In the web app, open **Slack** > **Automations** or **Discord** > **Automations** and, under **Prebuilt automations**, select **Triage Linear issue**, **Triage Jira issue**, or **Triage GitHub issue**. Choose the tracker in the **Trigger** card and the channel in the **Target** card, then select **Save automation**.

### Triage issues posted in a channel

If bug reports or tracker notifications already land in a Slack channel, run `/automations` there. In **Purpose**, choose **Triage engineering issues**, in **When to run**, choose **New channel message**, and select **Save and activate**. The automation is active right away, without a trial run, and runs on every new top-level message in the channel. See [Automations slash command](https://docs.coderabbit.ai/slack-agent/automations.md#automations-slash-command).

## Test it

Create a test issue in a team, project, or repository that the trigger watches. For the channel route, post a test bug report in the channel. See [Test a trigger](https://docs.coderabbit.ai/automations/triggers.md#test-a-trigger).

## Check the runs

Each run is listed on the automation's page. See [Automation details](https://docs.coderabbit.ai/automations/manage.md#automation-details). A successful run leaves one comment on the new issue, a new thread in the Slack or Discord channel, or a reply in the thread of the posted issue, depending on the route.

## Variations

* **Only some tickets.** These templates run on new tickets. To triage only new tickets created with a given label or status, set the **Filter** row in the **Trigger** card to **Has label** or **Has status**. **Has status** isn't available for GitHub. See [Managed webhooks](https://docs.coderabbit.ai/automations/triggers.md#managed-webhooks).
* **From ticket to pull request.** Use **Implement PRs for labeled tickets** under **Implement code changes**, which opens a pull request when a ticket gets the label or status you choose. See [Turn labeled Linear issues into pull requests](https://docs.coderabbit.ai/automations/guides/linear-issue-to-pull-request.md).
* **GitHub issues without an automation.** [Issue Enrichment](https://docs.coderabbit.ai/issues/enrichment.md) already comments on new GitHub issues with possible duplicates, related pull requests, and suggested assignees.

## What's next

> [card] [Linear issue to pull request](https://docs.coderabbit.ai/automations/guides/linear-issue-to-pull-request.md)
>
> Label an issue you have reviewed and get a pull request with the fix.

> [card] [Automation triggers](https://docs.coderabbit.ai/automations/triggers.md)
>
> Narrow managed webhook triggers by team, project, label, or status.

> [card] [Triage support tickets](https://docs.coderabbit.ai/automations/guides/triage-support-tickets.md)
>
> Investigate customer tickets and draft a reply for your support team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.