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

# Reporting and Feedback

> Report on bug intake health and improve the support-to-engineering loop

Use Duckie Assistant agents for reporting and feedback. The reporting agent posts operational summaries. The feedback agent reviews runs, corrections, blocked issues, and outcome data to recommend improvements to Duckie configuration.

## What It Does

The reporting and feedback function:

* Posts a daily or weekly bug intake report to support and engineering stakeholders
* Tracks new bug reports, issue creation, duplicate rate, blocked issues, resolution outcomes, and customer follow-up status
* Highlights engineering questions waiting on customers or support
* Reviews rejected, rerouted, duplicate, or incomplete engineering issues
* Identifies weak repro checklists, missing context tools, bad issue templates, and routing problems
* Proposes updates to workflows, agents, guidelines, tools, categories, and reports

## Recommended Components

| Need                | Duckie component                 |
| ------------------- | -------------------------------- |
| Recurring report    | Scheduler deployment             |
| Reporting logic     | Duckie Assistant reporting agent |
| Inspect Duckie runs | Duckie Assistant MCP or Runs API |
| Read issue outcomes | Linear or Jira app tools         |
| Destination         | Slack app tools                  |
| Feedback review     | Duckie Assistant feedback agent  |

## Reporting Flow

```mermaid theme={null}
flowchart TD
  Scheduler["Scheduler deployment"]
  Scheduler --> Reporter["Duckie Assistant reporting agent"]
  Runs["Runs and analytics"] --> Reporter
  Issues["Linear or Jira issues"] --> Reporter
  Tickets["Support tickets"] --> Reporter
  Reporter --> Digest["Support and engineering digest"]
  Digest --> Stakeholders["Stakeholder Slack channel"]
```

## Feedback Flow

```mermaid theme={null}
flowchart TD
  Runs["Runs and tool traces"]
  Issues["Issue outcomes"]
  Corrections["Engineer and support corrections"]
  CustomerReplies["Customer follow-up results"]

  Runs --> Feedback["Duckie Assistant feedback agent"]
  Issues --> Feedback
  Corrections --> Feedback
  CustomerReplies --> Feedback
  Feedback --> Patterns["Recurring patterns and gaps"]
  Patterns --> Improvements["Checklist, workflow, agent, tool, and template updates"]
  Improvements --> Testing["Replay and batch testing"]
  Testing --> Deploy["Updated bug intake deployments"]
```

## Report Contents

Include:

* New customer-reported bugs
* Bug reports converted to Linear or Jira issues
* Reports linked to duplicate or existing issues
* Reports blocked on missing customer information
* Engineering questions waiting on support or customer response
* Issues resolved, shipped, closed as duplicate, not planned, or cannot reproduce
* Customer follow-ups sent and waiting
* Average time from report to engineering issue
* Average time waiting on customer
* Top product areas and severity bands
* Tool failures and sync failures
* Recommended improvements

## Example Digest Shape

```text theme={null}
Bug intake summary

Window: Previous business day

Volume:
- New customer-reported bugs: 27
- Engineering issues created: 11
- Linked to existing issues: 6
- Waiting on customer details: 5

Engineering loop:
- 8 engineering questions routed back to support
- 5 customer answers synced to issues
- 3 issues resolved and ready for customer follow-up

Risk:
- 2 priority customers waiting on engineering questions
- 1 high-severity report missing logs

Automation health:
- 89% repro checklist completion before issue creation
- 2 issue sync retries
- 4 engineer edits to issue template fields

Follow-ups:
- Add API version lookup for integration bug reports
- Split dashboard bugs into loading, permissions, and data freshness categories
```

## Improvement Actions

Common improvements include:

* Add a missing repro checklist field
* Change the issue template
* Add an internal log or product event lookup tool
* Add duplicate detection against issue titles and labels
* Tighten the customer follow-up prompt
* Add a human review gate for sensitive bug categories
* Add a routing rule for a product area or engineering team
* Update the stakeholder report to show blocked customer loops

<Tip>
  Measure the full loop, not only issue creation. A useful bug intake system should improve time to usable repro, time to engineering answer, and time to customer follow-up.
</Tip>

## Related Docs

<CardGroup cols={2}>
  <Card title="Scheduled Deployments" icon="clock" href="/deployments/scheduled-deployments">
    Run reports on a recurring schedule.
  </Card>

  <Card title="Duckie Assistant Agents" icon="robot" href="/agents/duckie-assistant-agents">
    Build reporting and feedback agents for Duckie system improvement.
  </Card>

  <Card title="Analytics" icon="chart-line" href="/analytics/overview">
    Monitor performance and trends.
  </Card>

  <Card title="Replay Testing" icon="clock-rotate-left" href="/testing/replay-testing">
    Test changes against historical bug reports.
  </Card>
</CardGroup>