Bug Reporting Template for Linguists

Please fill out all fields to ensure the bug can be properly triaged and sent to engineering.

1. Language:
(e.g., French, Japanese)

2. Platform / Environment:
(e.g., iOS app, Android app, Web, Desktop)

3. App Version / Build Number:
(e.g., 5.3.1, Build 20251109)

4. Screenshot / Video:
(Attach visual evidence of the issue)

5. Steps to Reproduce:
(List clear, step-by-step instructions to recreate the issue)

6. Expected Behavior (Localized):
(What should the correct translation or behavior be?)

7. Actual Behavior (Localized):
(What is currently happening?)

8. Source String (if applicable):
(Include the original English string)

9. Localized String (if applicable):
(Include the problematic localized string)

10. Type of Issue:
(Choose one: Truncation / UI Overlap / Wrong Translation / Missing Translation / Encoding / Functional / Other)

11. Severity:
(Choose one: Blocker / Major / Minor / Cosmetic)

12. Additional Notes / Context:
(Any extra info that might help engineering understand the issue)

Subject: New Bug Reporting Template – Please Use for All Future LQA Issues

Hi [Linguist],

I hope you're doing well! As part of our effort to streamline the bug reporting process and reduce back-and-forth, we’ve created a standardized Bug Reporting Template for all LQA issues.

This template ensures that every bug you report contains the necessary information for engineering to understand, reproduce, and fix the issue without delays. Please use this template for every bug you submit, starting immediately.

Here’s how to use it:

Fill out every field in the template. If something doesn’t apply, write “N/A” rather than leaving it blank.
Be specific and detailed, especially in the “Steps to Reproduce” and “Expected vs. Actual Behavior” sections.
Attach screenshots or videos whenever possible. Visuals are critical for UI-related bugs.
Use consistent terminology (e.g., truncation, overlap, encoding) to help categorize the issue correctly.

You’ll find the template attached or available in our shared workspace [insert link or location].

If you have any questions or need help filling it out the first time, I’m happy to walk you through it. The goal is to make your reports actionable from the start so we can resolve issues faster and more efficiently.

Thanks so much for your attention to detail and collaboration!

Best regards,
Kevin