Skip to content

Submit feedback ​

Open Feedback → Submit feedback. The current form asks for a Title and Description. Both must contain text before submission.

Include these details

State the action, expected result, actual result, and steps to reproduce the problem. Include the file type or exact error when relevant, and read the submission result before assuming the feedback was saved.

Use it to describe a requested change or a reproducible problem. It does not correct the open document, restore lost work, or change a project's status.

Write a useful title and description ​

Name the affected task in the title. For example, “Returned bilingual file is rejected after external review” identifies a workflow more clearly than “It does not work.”

In the description, include:

  1. The page and action you used.
  2. The relevant file format and project type.
  3. The steps needed to reproduce the result.
  4. What you expected and what happened instead.
  5. The visible message, when one was shown.
  6. Whether the issue depends on a selection, filter, lock, or storage workspace.

Use an anonymized example when client material is involved. Do not put passwords, connection keys, or confidential source passages into feedback. The feedback feature's records can include title, description, and requester information; it is not a private note attached only to a translation segment.

Submit and read the result ​

Choose Submit and wait for the operation to finish. If the app reports that feedback was saved but its list could not refresh, the record may already exist; inspect the result before submitting a duplicate.

Read the result message to check whether submission succeeded. The form can clear even when submission fails. Keep a copy of a long description in case you need to retry.

The current form has no file-attachment, screenshot-upload, or conversation-thread controls. Describe the relevant message and provide the reproduction steps in its text fields. Saving feedback does not guarantee an immediate response, a scheduled change, or a fixed release date.

Use the right place for other information ​

InformationWhere it belongs
A question about a particular sentenceComment
Requirements for the current jobProject instructions
A reusable translation requirementAI rule
A task you need to completeTasks
A missing project or saved fileTroubleshooting and Storage and backups
An unsent example in the actual Title and Description fields. Review the information before choosing Submit feedback.
An unsent example in the actual Title and Description fields. Review the information before choosing Submit feedback.