Teamwork often includes discussions about particular keys, and the comments widget makes it easier to manage these conversations. Use it to leave notes and mention people with the @
symbol to get their attention.
Opening the comments widget
To leave a comment on a key, head to the project editor and click the Comments button under the key name.
Once you click the button, the comments widget (formerly called the "chat widget") will pop up.
At the top of the widget, you’ll see the name of the key you’re commenting on (for example, "welcome"). Unread comments will always appear at the top of the panel, so you never miss anything important.
You can also open the comments widget quickly by pressing Ctrl+Shift+M (or Cmd+Shift+M on a Mac) or by clicking the Comments button in the left-hand menu.
Messages in the comments widget
Writing a message and notifying other contributors
To leave a message, simply type it into the text box and press Enter. If you want to notify specific contributors, type @ followed by their name. Keep in mind that messages are limited to 1000 characters.
Once you post a comment, everyone mentioned with the @ symbol will automatically receive an email notification. You can manage your notification settings in your personal profile.
Editing and deleting messages
To edit or delete a comment, click the three dots (⋮) next to your message.
Navigating the widget
To jump to the translation key for a specific comment, click the arrow with a circle icon. The related key will be highlighted in yellow.
To go back to all comments for the project, click the left arrow icon at the top.
You can switch between projects within the comments widget by clicking the projects dropdown when viewing the list of all project comments.
To mark all comments as read, click the cog icon and select the appropriate option.
Please note: If you're browsing the list of all project comments, you won’t be able to write a new comment. Comments must be linked to a specific key or translation. To leave a comment, navigate to the relevant key or translation first.
Threads
Comments support threading to keep conversations organized. To start a thread, click Reply in thread under a comment.
The interface will look almost identical to the regular comments section.
You can resolve (close) a thread by clicking the checkmark icon in the top-right corner.
You can also resolve a thread from the all key comments view.
Once a thread is resolved, it won't appear in the list by default. To view resolved threads, click the filter icon in the comments list to include them.
Translation-level comments
You can also leave comments for specific translations by clicking the comments button next to the translation.
When you click this button, the regular comments widget will open.
In this case, you'll also see the language the comment is tied to (e.g., US English).
Translation-level comments appear in the list of all project comments and come with similar controls.
If you click View key in editor or Reply in thread, the corresponding translation will be highlighted, and all other keys will be filtered out.
Please note that contributors only have access to comments for the languages they work on. For example, if Bob has access only to French, he won’t see comments for US English translations.
Special notes
Adding comments
Comments must be linked to a specific key or translation; you cannot leave generic comments like in messaging apps.
When importing translation files that contain comments (e.g., Excel files), these will be treated as parent-level comments.
Replies to parent comments cannot be imported or exported.
Translation-level comments cannot be imported or exported.
Displaying comments
Views for key, translation, and thread comments will display the most recent 100 comments.
The project comments summary view will display all comments, but they will load in batches of 100.
Comments retention and persistence
Resolved comments (threads) are retained for 6 months after being marked as resolved. After that, they will be permanently deleted.
Comments are no longer saved in project snapshots and cannot be restored from a snapshot. Once a comment is deleted, it cannot be recovered.
Comments do not transfer when merging branches. For example, if you're merging
branch_b
intobranch_a
, comments frombranch_b
will be lost, and only comments frombranch_a
will be kept.