Issues Report (Classic)

This article is for Account Owners and Project Managers.

You can keep track of all source and translation issues from these three issues reports:

  • Source Issues Report
  • Translation Issues Report
  • Issues Details (Option to download the report or manage issues.)

You can download the report or view and manage the issues. The information displayed in the download report will provide you with full detail from the issues in the order they were entered. This data will help prevent similar roadblocks in the future.

Access the Issues Report

  • Go to Reports > Issues.
  • At the top right of the page, select from the following tabs: Source Issues, Translation Issues, and Issues Details. 

Issue Reports

Source Issues: This report displays data for all open source issues within the selected date range. You can request this data across multiple projects. In Smartling, there are two sub-types of source issues:

  • Clarification 
  • Misspelling

Translation Issues: This report displays data for all translation issues within the selected date range. In Smartling, there are five sub-types of translation issues:

  • Review Translation
  • Doesn't Fit Space
  • Placeholder Issue
  • Poor Translation
  • MT Error

Subtypes can be customized for the account. Contact your Customer Success Manager to request custom subtypes. They are specific to either source or translation type.

Issues Details: This report contains data for all issues: opened/closed and source/translation with complete information for the selected date range. This data can only be obtained by downloading the CSV file. The following fields are included in the report:

The export contains the following details;

  • Issue #
  • Issue uid
  • Issue type
  • Issue subtype
  • Source Text
  • Translation Text
  • Language
  • Issue state
  • Issue severity
  • Issue/Comment text
  • String Key
  • String Variant
  • String hashcode
  • Issue open date
  • Issue close date
  • Issue/Comment date
  • Issue answered
  • Issue reporter/commenter uid
  • Issue reporter/commenter name
  • Issue reporter/commenter email
  • Project id
  • Project name
  • Job ID
  • Job (name)
  • Job Issue assignee uid
  • Issue assignee name
  • Issue assignee email


Was this article helpful?