Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

JSM - Data Center to Cloud migration - language support reviews after migration

Pavol Gocal
Pavol Gocal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
July 7, 2026

Hello,

we are migrating from Jira DC to Cloud. In our service management projects, we have multiple language supports for different languages.

After migration to Cloud (so far in test sandbox), the language support for each language requires reviews:

missingDefaultValues.pngslovakLanguage.png

multipleLanguages.png

Is there a way to automatically migrate and accept reviews for different languages? So that we do not have to review all the changes in all our projects? Or maybe what are the steps to make it easier?

Thank you for your help.

Answer
Watch
Like Ismail Bin Ibrahim likes this
245 views

3 answers

2 accepted

1 vote
Answer accepted
Germán Morales
Germán Morales
Community Champion
July 7, 2026

Hi @Pavol Gocal , what you're describing matches a known Jira Service Management Cloud bug, not a default language issue: JSDCLOUD-9553 and JSDCLOUD-15471, where Portal content, Components and customer visible statuses get flagged as "needs review" even when the translation is already correct.

The workaround Atlassian confirms: go to Project settings > Request types > Workflow statuses, add a trailing space to the "Status name to show customer" value for each affected language, then save. That re-triggers the translation and clears the warning for that section.

There's no bulk accept option, you have to repeat this per project and per language. If this affects several projects, it's worth voting both tickets to push for a real fix.

Reply
1 vote
Answer accepted
Marc -Devoteam-
Marc -Devoteam-
Community Champion
July 7, 2026

Hi @Pavol Gocal 

Welcome to the community.

Please check you space default language:

On migrations spaces often default to the cloud instance's regional settings instead of preserving the original data center project's language (e.g., overriding English UK with English US).

You will need to fix this manually by setting the correct default language

Reply
0 votes
Kvitka Martsynyshyn
Kvitka Martsynyshyn
Contributor
July 21, 2026

I've seen similar questions during Jira Data Center → Cloud migrations. Unfortunately, multilingual content often requires review after migration because Cloud handles translations and localized content differently than Data Center. There isn't a built-in way to automatically accept all language reviews across projects. If you have many service projects, it's worth testing a representative project first to understand the scope of the required reviews before your production migration.

Reply

Suggest an answer

Log in or Sign up to answer
Jira Service Management
Jira Service Management
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security