Skip to content
Mimic Docs

Feedback and Triage

Use the feedback pipeline to capture operator context and turn it into tracked execution work items.

Capture paths

  • Global overlay button in app navigation: Feature Request / Bug Report
  • Workflow-specific reporting from org dashboards: workflow issue reports with claim/evidence context

Each submission can include:

  • Current route and URL
  • Browser telemetry snapshot (console + network buffers)
  • Optional VM instance context

Global overlay submissions (Feature Request, Bug Report) auto-capture a screenshot before opening the form. Workflow issue reports from org dashboards are log/context driven and do not include manual screenshot selection or upload fields. Submission org assignment follows effective org context. For super admins, the active org override controls which org owns the new submission.

Org dashboard feedback loop

  1. Open /app/org-dashboard/{orgKey}/flagged.
  2. Expand a flagged claim and verify Issue, Expected, Found, and Action fields.
  3. Select Report feedback to open workflow issue reporting with claim context prefilled.
  4. Add focused notes and targeted log excerpts, then submit.

When available, the modal includes:

  • Batch and job linkage (batchId, jobId, agentId)
  • Workflow-pack/runtime identifiers
  • Worker log text for targeted excerpt selection
  • Claim-linked evidence references

Triage surfaces

  • Super admin queue: /app/admin/feedback
  • Super admin detail page: /app/admin/feedback/{submissionId}
  • Org workflow issue list: /app/org-dashboard/{orgKey}/feedback

Queue actions

  • Filter by type, status, organization, VM, and date range
  • Update submission status (open, in_progress, resolved, closed)
  • Export filtered submissions as CSV
  • Pause or resume work-item sync
  • Rearm enrichment, GitHub sync, or ClickUp sync

External sync model

Feedback automation can enrich and sync to:

  • GitHub issues
  • ClickUp tasks

Webhook consumers (/api/webhooks/github/feedback, /api/webhooks/clickup/feedback) request status resync on linked work items after external updates.

Operational guidance

  • Require actionable acceptance criteria in reports.
  • Pause sync for noisy submissions until triage clarifies scope.
  • Keep the automation path deterministic: use evidence-backed routing before manual fallback.