Add QA Info Button To Describe Issues During Testing

Feature: In-App Issue Reporter ("Report an Issue")

What it is: A lightweight reporting control, surfaced as a persistent info button on every screen, that lets a tester flag a problem the instant they hit it. No leaving the app, no switching to email or Slack, no losing the moment.

The problem it solves: During open testing, the highest-value feedback is the friction a tester feels in the flow. That signal is usually lost, because reporting it means stopping, opening another tool, and reconstructing what happened from memory. This closes that gap by capturing the issue at the point and moment it occurs.

How it works:

• Context auto-capture: The "Reporting an issue on" field prefills the tester's current context (the active screen, session, or date) so they never have to describe where they were. It stays editable in case the auto-detected context is off.

• Plain-language prompt: "What went wrong?" asks for expected behavior versus what actually happened. That framing trains testers to file useful, reproducible reports instead of vague ones, with a 5,000-character ceiling for detail when it matters.

• Screenshot attached by default: "Include a screenshot of this page" is pre-checked, so visual evidence rides along automatically. The tester can opt out, but the default guarantees engineering gets what it needs on most reports.

• One tap to send: Cancel or Send report. The report leaves with full context, description, and evidence bundled together.

Why it is best-in-class:

• In-context, zero-friction: Reporting lives where the problem happens, so testers actually use it. Adoption is the whole game with QA tooling, and friction kills adoption.

• Structured but human: The context and screenshot are captured for you; the description is guided rather than templated. You get consistent, triageable reports without making testers fill out a form.

• Evidence by default: Auto-attached screenshots turn "it looked weird" into a reproducible finding, which is where most bug reports fall apart.

• Built for the testing window: It matches how the open window actually runs. Testers move fast across the flow, and this lets them leave a trail without breaking stride.