Concourse Feedback

We would like to share a request that has come up in a project involving members of multiple nationalities: the need to view Jira content in each member's preferred language. Accordingly, we would like to ask for your consideration regarding the addition of multilingual support functionality in Jira.

■ Background & Purpose

• In projects involving members of multiple nationalities, there is a concern that language differences may lead to gaps in understanding of Jira content.

• We would like to establish an environment where each member can accurately understand ticket content in their own language, thereby ensuring smoother project operations and reducing communication loss.

■ Requirements (What We Would Like to Achieve)

• We would like to enable multilingual support for the "Summary (Title)" and "Description" fields of tickets.

• Examples of the functionality we envision are as follows:

  • Automatic translation display of registered content

  • Side-by-side display in both Japanese and English

  • Language switching on a per-user basis

• We are open to any alternative approach that can achieve the same objective, and would welcome your suggestions.

■ Additional Notes When we consulted Rovo in advance, it proposed an approach that combines Jira Automation with an external translation API to automatically translate the "Description" field upon ticket creation. We would appreciate your feedback on the feasibility and advisability of this approach as well.

[Rovo's Response: Automation + External Translation API Approach]

If you wish to continuously "automatically translate and reflect the description," one option is to combine Jira Automation with a translation API.

Configuration Overview:

• Trigger

  • "When an issue is created"

  • Or, "Manually execute the rule once against all issues via JQL"

• Action 1: "Send Web Request"

  • Send a request to a translation API (e.g., DeepL API, Google Cloud Translation)

  • Pass {{issue.description}} in the request body

• Action 2: "Edit Issue"

  • Set the translated text contained in the API response body into the "Description" field

Points to Note:

• A contract and authentication key for the translation API are required.

• Be mindful of the monthly execution limit for automation rules.

• If executing against all existing issues at once, consider splitting the rule depending on the number of issues.