Problem

After changing the system default language from English (US) to English (UK), existing Jira Service Management (JSM) projects still retain English (US) as the default language. English (UK) is added as a secondary language, requiring manual review and copy/paste of translations for each section (e.g., request types, portal announcements) in every project. 

Suggested Solution

Introduce a bulk operation or admin tool that allows site administrators to:

• Copy all English (US) portal translations to English (UK) across selected JSM projects in one action.

• Optionally, set English (UK) as the new default and remove English (US) from those projects after confirming the migration.

• Ensure that custom text is not overwritten without admin review, but streamline the process for bulk migration where the content is identical.

Why This Is Important

• Reduces significant manual effort and risk of human error when standardizing language settings across many projects.

• Supports organizations migrating to UK data residency and wishing to align all service spaces with English (UK) as the sole language.

• Improves consistency and user experience for both admins and end users by ensuring language settings are correctly and efficiently applied.

Workaround

Currently, the only supported method is to:

• Manually add English (UK) to each project via Project settings → Language support.

• Review and copy/paste each section's translation from English (US) to English (UK).

• Set English (UK) as the default and remove English (US) after confirming all translations.
  This process must be repeated for every project and section, which is time-consuming and error-prone for large instances.