Triage reported issues
Review the engine changes proposed from a Jira issue, apply or dismiss each suggestion, and choose which connected content to retranslate.
A reported translation problem can have several causes. The wording may use the wrong product term, the source may omit context, or correct text may be clipped by the interface. A Jira ticket in Queue brings the report together with proposed glossary, rule, and brand-voice changes for your team to review.
Open Queue, use the Kind filter to show Triage items, and select the ticket. The Jira integration instructions explain how to connect the site, choose its engines, and label an issue lingo.
Read the report and its suggestions #
Read the affected source and target, locale, location, and revision in the Jira issue. Use surrounding text or a screenshot to check an ambiguous or clipped message.
On the ticket's Suggestions tab, inspect each proposal's engine, explanation, locale, and destination resource. For an update, compare the existing guidance with the proposed replacement. Check other engines that share that resource before changing it.
An incorrect product term can support a glossary change. A missing catalog or layout defect needs work from the application owner. If the report omits the wording or locale, clarify it in Jira before applying a proposal.
Apply or dismiss each suggestion #
Choose Apply to save a useful proposal immediately, or Dismiss when it is irrelevant, redundant, too broad, or unsupported by the report. Applying or dismissing requires org:suggestion:edit together with edit access to the engine, or an explicit grant to that engine for an organization member. Check suggestion permissions if either action is unavailable.
After applying, open the saved glossary term, rule, or brand-voice variation and verify its wording and locale. Review suggestions explains how to check its effect on a fresh translation.
Once generation has finished and every suggestion has a decision, Lingo.dev posts a summary comment on the Jira issue. If no engine proposes a change, the summary says so. Use the issue's normal Jira status to track whether the reported problem is resolved.
Retranslate affected content #
After applying a suggestion, open the ticket's Retranslate tab. Check the listed GitHub, Zendesk, or Payload CMS integrations and their affected target locales. Select the integrations to update and choose Retranslate. This action requires org:manage_integrations.
Retranslation covers each selected integration's entire configured scope in those locales. It can replace accepted translations and consumes normal translation usage. Check that scope before starting it.
Follow the linked runs and inspect the destination content. For GitHub, review the files, source revision, locales, and translated diff before merging. For Zendesk or Payload, check the translated fields and draft or published state in the CMS. Applying guidance and releasing regenerated content are separate decisions.
End a ticket or start a new round #
Remove lingo from the Jira issue, close it, or delete it to close the Queue ticket. Pending suggestions are dismissed unless another open ticket still cites them. Applied changes and completed translations remain.
Reopen the issue with lingo present, or re-add the label to an open issue after its ticket closes, to start another round. Keep the earlier report and outcomes so reviewers can see what has already changed.