Dev + Support workflow

Reduce back-and-forth on bug tickets

Support teams can package clearer details before escalation. Developers get structured context, QA gets a checklist, and customer updates stay consistent.

Markdown handoffQA checklistJSON export

Fields filled

Repro steps

Priority

Medium

Input

Ticket details from support

Ticket IDAffected area

Issue title

Issue typeImpactEnvironment

Customer impactSteps to reproduce (one per line)

Expected behaviorActual behavior

Errors / logsWorkaround (if any)

Actions

Export a clean handoff

Fill the fields once and copy a clean handoff to dev and QA.

QA checklist

- [ ] Repro steps not provided yet.

Developer handoff markdown

# Support-to-Dev Handoff

- **Ticket**: Unassigned
- **Title**: Untitled issue
- **Type**: Bug
- **Impact**: Medium
- **Affected area**: Unknown module
- **Environment**: Environment not provided

## Customer Impact
Customer impact details not provided.

## Reproduction Steps
1. Repro steps not provided yet.

## Expected Behavior
Expected behavior not provided.

## Actual Behavior
Actual behavior not provided.

## Errors / Logs
No technical error details attached.

## Workaround
No workaround confirmed yet.

## QA Verification Checklist
- [ ] Repro steps not provided yet.

Support summary

Issue "Untitled issue" has been packaged for engineering triage. Priority is medium and currently affects the affected module. Customer impact: impact details are being validated. No stable workaround is confirmed yet.