This article explains how a language tester can report an issue.
The dialog to enter an issue has one more of the following fields. Fields may be optional or mandatory, depending on the quality profile that the project manager selected for this language test.
The priority indicates how fast an issue must be resolved.
|None||Translation preferential change (not applicable for non-translation issues).|
Nice-to-have functional or source text improvement; small linguistic issues like minor spelling or punctuation mistake.
|Medium||Does not affect the usage of the functionality, but impacts user experience, e.g. meaning mistake, grammar error.|
|High||Causes great difficulty in using functionality or impacts confidence in the product .|
|Very high||Showstoppers, interruptions of business or loss of data.|
The severity indicates how bad an issue is for the usability.
Neutral / None
|Improvement, nice to have.|
Errors that do not affect the usage of the functionality.
Causes great difficulty in using functionality or impacts confidence in the product .
Showstoppers, interruptions of business or loss of data.
|Error category||The error categories depend on the quality framework. An error category may have sub-categories. You can select main and/or sub-categories.|
|Suggested translation||Suggest a better translation here.|
Hint: use the short-cut icon to copy the current translation, and then do a quick edit.
The translation at the moment that you create this issue.
Note: this translation will be stored with this issue, even if the translation is later changed.
The source text at the moment that you create this issue.Note: this source text will be stored with this issue, even if the source is later changed.
|Selected string ID||Unique identifier of the selected string.|