# Turn tagged Dixa bug reports into clean Linear issues

> When a Dixa conversation is tagged as a bug, we write a clear engineering issue in Linear and link it back on the ticket so support can follow the fix.

- Workflow type: agent
- Services: Dixa, Linear
- Categories: Customer Support, Engineering
- Published: 2026-07-17

## What it does

- Checks Dixa every 20 minutes for customer conversations tagged as bugs or defects.
- Reads the full conversation and drafts a clear issue with steps to reproduce, expected versus actual behavior, and how many customers are affected.
- Files the issue in the Linear team you choose, then posts the issue link back onto the Dixa conversation so support can track the fix.
- Checks each conversation first so the same bug is never filed twice.

## What you'll need

- A Dixa account where bug conversations get a consistent tag, like 'bug' or 'defect'.
- A Dixa login that can read conversations and add internal notes.
- A Linear workspace and the team that should receive new engineering issues.

## Prompt

Every 20 minutes, scan Dixa for customer conversations tagged as bugs and turn each new one into a well-formed engineering issue in Linear, then link that issue back onto the Dixa conversation so support agents can follow the fix.

Let me configure two things up front: which Dixa tag marks a conversation as a bug or defect (for example 'bug', 'defect', or 'regression'), and which Linear team new issues should be filed under. Use those two values throughout the run.

To find candidates, use Dixa's Search conversations with filters to pull recent conversations, and use List conversation tags on each one to confirm it actually carries the watched bug or defect tag. Only continue with conversations that genuinely have that tag.

Before filing anything for a conversation, call List internal notes on it and check whether it already contains a Linear issue link. If a Linear link is already present, skip that conversation so the same bug is never filed twice.

For each new tagged conversation, use List messages to read the full thread and gather the reproduction details and customer impact. Do not invent steps that are not supported by the conversation; if a detail is missing, say so plainly in the issue rather than guessing.

Draft a clear engineering issue: a concise, specific title, and a description that includes steps to reproduce, expected versus actual behavior, and how many customers appear to be affected. File it in Linear with Create Issue under the configured team.

Finally, close the loop: post the new Linear issue back onto the originating Dixa conversation with Add internal note. Keep the note short, with the issue title and its Linear URL, so support agents can follow the fix from inside Dixa.

## How to customize

- Choose which Dixa tag is watched, for example 'bug', 'defect', or 'regression'.
- Pick which Linear team new issues are filed under.
- Adjust how often it runs, from every few minutes to once a day.

## FAQ

### How does it avoid filing the same bug twice?

Before creating anything, it checks the conversation's internal notes for an existing Linear link and skips it if one is already there, so a conversation is never filed twice.

### Which conversations get turned into issues?

Only conversations that carry the Dixa tag you choose to watch, such as 'bug' or 'defect'. Everything else is ignored.

### Will support agents know an issue was created?

Yes. The Linear issue link is added as an internal note on the Dixa conversation, so agents can follow the fix without leaving Dixa.

### Can I send issues to a specific Linear team?

Yes. You choose which Linear team receives the issues when you set this up, and you can change it any time.

### Does it write the bug report for me?

Yes. It reads the whole conversation and drafts a title and description with steps to reproduce, expected versus actual behavior, and the number of customers affected.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-tagged-dixa-bug-reports-into-clean-linear-issues