In a nutshell
With Translations for Confluence, you can create knowledge bases in several languages. JSM customers and agents can read these articles in the help center (customer portal) and see the language version that suits them.
Read our blog post about this feature (focus on Data Center/Server) Create a multilingual knowledge base in Jira Service Management
Accessing Confluence knowledge-base articles from JSM
Thanks to the integration between Confluence and JSM, knowledge-base articles written in Confluence can be opened directly in the help center. Translations for Confluence shows each reader the language version that fits them, provided that a translation exists.
Which language is displayed in JSM?
The app checks the following sources in order and uses the first one for which the page has a matching translation. Which sources apply depends on the reader's account type. See Manage JSM customer accounts.
Users with a Confluence license (for example agents)
-
The language chosen with "Change language" in Confluence. See the special case below.
-
The language from the user's profile.
-
The browser language.
-
The site's default language.
-
The first language macro on the page.
Customers with a portal-only account
-
The language from the user's profile.
-
The browser language.
-
The site's default language.
-
The first language macro on the page.
Customers with a portal-only account can't open Confluence, so they can't save a language with "Change language".
Visitors who aren't logged in (anonymous)
-
The browser language.
-
The site's default language.
-
The first language macro on the page.
Visitors who aren't logged in have no profile, so the known limitation doesn't affect them: they see the article in their browser language.
Special case: "Change language" in Confluence also applies in JSM
When a logged-in user picks a language with Change language in Confluence, the app stores that choice for the user's account. The choice:
-
applies everywhere: on every Confluence page with translations, and also for knowledge-base articles in JSM;
-
comes first: it beats the profile language, the browser language and all other settings;
-
stays in place until the user picks another language in Confluence. This also applies to "All languages": if the user picks it, JSM shows all language versions too.
This explains why two users with the same profile language may see different versions in JSM: one of them has already chosen a language in Confluence.
Tip: for users with access to Confluence, this is currently the most reliable way to see the right language in JSM. Open any page with translations in Confluence once, choose the language under Change language, then open the article in JSM again.
The language switcher isn't available in JSM
In the help center, Atlassian doesn't show the elements the app uses for its language switcher ("Change language" in the page header or page menu). Readers therefore can't change the language directly in the help center.
Prerequisites
-
The knowledge-base space must be readable by your readers. Check Space settings → Permissions, and for visitors who aren't logged in, enable anonymous access. In JSM, set the knowledge base's "Who can view" accordingly.
-
Restricted pages: if a page has its own restrictions, the app needs access to it. Otherwise, it can't detect the page's languages. See Using Translations macros with content restrictions.