Issues
Record source questions, target-language findings, comments, replies, resolution, and participant confirmation in threads tied to project content.
Where Issues are available
Open Issues from the project sidebar to review threads across the project. The same issue experience can also open inside the Editor with a file, target language, current row, or selected row range already in context.
Create a report or comment
- Choose Report when a question or finding needs a tracked resolution. Choose Comment for contextual discussion that does not use the report resolution lifecycle.
- Choose Source for a language-independent source issue, or Target and a target language for translation-specific feedback.
- Select one or more categories such as accuracy, terminology, style, source error, or context gap, then write the message. In the Editor, use row mentions to attach the exact current row, selected range, or another row.
Filter and read a thread
The left list is the project or file inbox; the detail panel shows the selected thread, its messages, attached rows, snapshots, participants, and available actions. New activity can arrive while the view is open, so the selected thread and list update without becoming separate copies.
- Filter by type, status, language, file, item, or category. Selecting a chip in a thread can apply the matching filter, and Clear filters restores the full available set.
- Source threads appear as Source; target threads display their target language. AI-review and LQA findings may also show origin and severity information.
Resolve, confirm, or reopen
- Open means the report still needs an answer or decision. Mark answered moves it to Solved after the response has been recorded.
- When confirmation is required, each required viewer confirms the answered report. Closed means the required confirmation flow has completed; the detail shows confirmed and pending participants.
- Reopen returns a solved or closed report to Open and clears the current viewer-confirmed state so the new discussion can be reviewed again.
- Comments are labeled Comment rather than Open, Solved, or Closed because they do not follow the report resolution lifecycle.
Content safety and deletion
An issue can include the source or target text as it appeared when the thread was created. Use that attached text to understand the original report, then compare it with the current Editor content before deciding that the problem is resolved.
- Report
- A tracked question or finding that can move through Open, Solved, and Closed.
- Comment
- Contextual discussion that does not use the report resolution states.
- Confirmation
- Shows whether required participants have acknowledged the resolved outcome; it is separate from changing the report to Solved.
- Open Issues from the project sidebar, or open it from the affected row in the Editor.
- Choose Report or Comment, then choose Source or the relevant Target language.
- Select categories, attach the exact row or range when available, write the message, and send it.
After completion: The new thread appears in the Issues list with its type, content scope, categories, message, and attached rows available to project participants who can view it.
Problem
A row mention cannot be sent.
What to do
Choose a row available in the current file, or remove the unresolved mention. A mention that does not match an available row is not saved.
Problem
An issue no longer appears after filtering.
What to do
Use Clear filters, then check type, status, language, file, item, and category filters. A status change can move a thread out of the current filtered set.