Use Cases

Common ways teams use Screendesk Bug Reports in QA, support, and product workflows.

Common ways teams use Screendesk Bug Reports in QA, support, and product workflows.

Pick the scenario closest to yours.

Use case

Capture bugs during manual QA. Share one link with full context.

Jump to

Manual & exploratory testing

Use case

Let users report issues from inside your app. Cut support back-and-forth.

Jump to

End user bug reporting

Use case

Let clients report bugs on their own machine. Great for agencies.

Jump to

Client bug reporting solution

Use case

Turn monitoring alerts into clear repros. Add richer debugging data.

Jump to

Expand on monitoring errors

Use case

Hand off manual flows to automation. Start E2E scripts faster.

Jump to

E2E testing handover

Use case

Capture “what just happened”. Save the last minutes without redoing the bug.

Jump to

Individual monitoring

Manual & exploratory testing

Use this during manual QA and exploratory testing.

Capture issues once. Share one link with the exact repro steps.

• Capture with Screenshot, Video Screen Recording, or Instant Replay.
• Include the debugging context engineers need. This includes logs and requests.

End user bug reporting

Use this when customers hit bugs in production.

Use the screen recording links. Users can submit reports in-context.

• Reduce support back-and-forth. Get a repro instead of long threads.
• Capture technical context automatically. Engineers debug faster.
• Works well with helpdesks like Intercom and Zendesk.

Client bug reporting solution

Use this if you build products for clients.

Install the Screendesk extension on the client’s browser. They can report issues themselves.

• Get better bug reports without chasing screenshots and logs.
• Works well for environment-specific and permission-specific bugs.
• See Browser support for supported browsers.

Expand on monitoring errors

Use this when monitoring catches exceptions, but repro is unclear.

Screendesk complements tools like Sentry, Rollbar, and Datadog.

• Turn an alert into a reproducible flow.
• Capture what happened plus logs, requests, and environment details.
• Verify the fix with a new capture.

E2E testing handover

Use this to hand off manual test flows to automation.

Record the flow once. Hand it to an automation engineer.

• Share the exact steps and expected behavior.
• Reduce ambiguity around timing and navigation.
• Use the E2E helper to generate a starter test template.

Individual monitoring

Use this for “it just happened” bugs.

Enable Instant Replay to keep a rolling buffer.

• Capture the last ~2 minutes without redoing the repro.
• Great for flaky UI, timing issues, and intermittent errors.
• Nothing uploads until you click Save.