Jira translation triage
Turn labeled Jira feedback into engine suggestions, review each change, and choose which connected content to retranslate.
A translation issue often reports a visible symptom: the wrong product term, an English button in a translated screen, or text that no longer fits. Connect Jira to bring that feedback into Queue, where you can review proposed glossary, rule, and brand-voice changes for the engines you choose.
In the Studio 2.5 navigation, open Studio 2.5 → Integrations instead of Settings → Integrations. Existing connection and setup links still work.
Choose Apply or Dismiss for each suggestion. After applying changes, use the ticket's Retranslate tab to decide which connected content to regenerate.
Connect Jira and describe the occurrence #
The integration supports Jira Cloud, including Jira Service Management Cloud, and comes with the Enterprise plan. See pricing for current availability.
- Open Queue → Settings in the intended Lingo.dev organization.
- Under Triage sources, select Connect and authorize the Jira site through Atlassian OAuth. Account connections are managed in Settings → Integrations.
- Back in Queue settings, select Choose engines for the site. Choose the localization engines its issues may change, then select Save.
The site needs at least one selected engine before its issues produce suggestions. Saving the selection also picks up existing open issues labelled lingo. A site can belong to only one connected organization at a time. Jira comments use the authorizing identity; use an appropriate shared account if the team needs shared attribution.
Connecting the site, choosing its engines, and retranslating require org:manage_integrations. Applying or dismissing a suggestion requires org:suggestion:edit together with edit access to its engine, or an explicit grant to that engine for an organization member. Suggestion permissions explains how to grant access.
Give the issue enough information to investigate:
- The affected locale, exact source and displayed target text, and their location or revision.
- The expected result and observed problem. Include a screenshot or space constraint for a presentation issue.
- The application or localization engine involved, plus any terminology decision already approved.
For example: “In es-MX checkout, the source button says ‘Place order,’ but the displayed target remains English at revision X.” The report identifies an untranslated occurrence without assuming that a glossary entry is the repair.
Add the case-insensitive label lingo to an open issue. Lingo.dev reads its summary, description, and comments and proposes changes for the site's selected engines. Open Queue, use the Kind filter to show Triage items, and select the ticket to review its suggestions.
Updates to a labelled issue can also bring it into Queue. A ticket that is already open keeps its current round of suggestions.
Match the proposed repair to the problem #
Read the reported occurrence before applying a suggestion. Some problems need shared translation guidance; others need an application or delivery change.
| Reported problem | What to establish |
|---|---|
| An incorrect product term in one language | The intended term, locale pair, and localization engine whose glossary should change. |
| An unexpected Korean date format | Whether the value is translated text or is produced by an application formatter. |
| German text overflows a navigation control | Whether concise wording can preserve meaning within the available width, or the component needs a layout change. |
| Several languages display source text | Whether translations were generated, loaded, and selected for each locale. |
| API traffic returns 429 | Whether the issue concerns translation wording at all, rather than an API limit. |
For a missing catalog, date formatter, or layout defect, assign the repair to the application owner. Use a glossary, rule, or voice change when it addresses the wording requirement in the report.
Apply or dismiss each suggestion #
Open the ticket's Suggestions tab. For each proposal, inspect the localization engine, language, explanation, and destination resource. Suggestions can:
- Add or update a glossary term.
- Add or update a translation rule.
- Add or update a brand-voice variation.
Choose Apply to save that change immediately, or Dismiss to leave the guidance unchanged. Check for duplicate or conflicting guidance and inspect other engines that share the destination resource. After applying, open the saved term, rule, or voice variation to verify it.
Once generation has finished and the ticket's suggestions have been decided, Lingo.dev posts a Jira comment summarizing the outcomes and linking to Queue. If no engine proposes a change, the summary says so. Close the Jira issue through your team's normal process after checking the result.
Decide whether to update existing translations #
After applying a suggestion, open the ticket's Retranslate tab. It lists affected GitHub, Zendesk, and Payload CMS integrations and the target locales the changes concern.
Select the integrations to update, check their listed locales, and choose Retranslate. This regenerates the entire configured scope of each selected integration in those locales. It can replace accepted human edits and incurs normal translation usage.
Follow each run and inspect the result in its destination: the repository diff or pull request for GitHub, or the translated content and publication state in Zendesk or Payload. Review and merge or publish through the normal process. You can leave retranslation for later; the applied guidance remains saved.
Recover or end triage #
Removing the lingo label, closing the issue, or deleting it closes its Queue ticket and dismisses pending suggestions that no other open ticket cites. Applied changes remain saved. Reopening an issue with the label present, or re-adding the label to an open issue after its ticket closes, starts a new round of suggestions with the earlier history retained.
If an expected ticket is missing, check that the issue is open, carries lingo, and belongs to a connected site with engines selected under Queue → Settings. Check the organization's plan and the connection's status. If a ticket remains processing after connection access is restored, share its link with Lingo.dev support.
Manage account authorization and disconnection in Settings → Integrations. To stop new issues from producing suggestions while keeping the connection, clear its engine selection in Queue → Settings and save. End existing tickets in Jira separately.
Jira webhooks are renewed on a schedule. If updates stop arriving, check site authorization and connection health; reconnect when access needs to be restored. Revoke the OAuth grant separately when provider access should end. Existing comments, applied guidance, and completed translation output remain.