Back to Crowdin in Google Sheets
SheetXAI logo
Crowdin logo
Crowdin · Google Sheets Guide

Export Crowdin QA Check Issues to a Sheet for a Translation Audit

2026-05-13
4 min read
See the Excel version →

The Scenario

You are a QA lead on the localization team. The sprint review is tomorrow at 10 AM and the translation manager has asked you to audit all open QA check issues in the main Crowdin project before the call.

What leadership actually needs is a Google Sheet, one row per issue, with the issue type, affected language, string identifier, and validation level. They want to assign fixes to translators before end of day.

The slow version:

  • Open Crowdin's QA checks panel
  • Filter by project, click through issues language by language
  • Copy issue details into a spreadsheet manually
  • Miss three issues because the filter was wrong
  • You walk into the 10 AM review with an incomplete list and no assignments made.

The fast version is one prompt.

The Easy Way: One Prompt in SheetXAI

SheetXAI is an AI agent inside your spreadsheet that pulls every QA check issue from Crowdin and writes it into the sheet, so you have a complete list before the morning review.

Open the SheetXAI sidebar and type:

List all QA check issues in Crowdin project ID from cell A1 and write the issue type, language, string identifier, and validation level into my sheet starting at row 2. Sort by validation level descending so the most critical issues are at the top.

SheetXAI calls the Crowdin API, retrieves every open QA issue, and writes them into the sheet sorted by severity. The audit list is ready before the morning coffee is done.

What You Get

A QA audit sheet with one row per issue:

  • Issue type — spelling error, consistency violation, formatting mismatch, etc.
  • Language — the target language with the issue
  • String identifier — the exact string key in Crowdin
  • Validation level — critical, major, or minor

The validation level sort is what makes the list actionable. A QA audit with 200 issues sorted by language is a wall of noise. The same list sorted by validation level descending means the team addresses the critical issues before the review and the minor ones can wait.

Add a column E for the assignee once the list is in the sheet, and you have a ready-made task board.

What If the Data Is Not Quite Ready

QA audits rarely need a raw dump of all issues. The team usually needs a specific slice.

When you only need critical issues from specific languages

The sprint covers five languages and you only have bandwidth to fix critical issues this week.

List all QA check issues in Crowdin project ID from cell A1 where the validation level is critical and the language is one of the languages listed in column A of the Languages tab. Write the issue type, language, string identifier, and validation level into my sheet.

When you want to group issues by translator for assignment

Each language has a lead translator whose name is in the Translators tab. You want the audit sheet pre-assigned.

List all QA check issues in Crowdin project ID from cell A1. Write issue type, language, and string identifier into columns A through C. Look up the translator for each language in the Translators tab and write the translator name into column D. Sort by translator name so all issues for each translator are grouped.

When you need to track which issues were present in the last sprint

You have last sprint's audit in the Prev Sprint tab. You want to see which issues are new this sprint.

List all QA check issues in Crowdin project ID from cell A1. Write issue type, language, and string identifier into columns A through C. In column D, write "NEW" if the same string identifier and language combination does not appear in the Prev Sprint tab, and "REPEAT" if it does.

When you need the full audit with issue counts per language for the sprint review slide

Leadership wants a summary table, not the raw list. One row per language, showing how many critical, major, and minor issues each has.

List all QA check issues for Crowdin project ID from cell A1. First, write all raw issues into a hidden tab called Raw Issues. Then, in the main sheet, write a summary table: one row per language with columns for language name, critical issue count, major issue count, minor issue count, and total count. Sort by total count descending.

The pattern: pull the raw issues and aggregate the view in one prompt. The sheet becomes the sprint review artifact.

Try It

Get the 7-day free trial of SheetXAI and open a sheet with your Crowdin project ID in cell A1, then ask it to pull all QA check issues. The Crowdin integration is included in every SheetXAI plan. For related workflows, see how to pull a translation progress dashboard or the Crowdin in Google Sheets overview.

Stop memorizing formulas.
Tell your spreadsheet what to do.

Join 4,000+ professionals saving hours every week with SheetXAI.

Learn more