Issue Summary

This is reproducible on Data Center: yes

If priorities named “Blocker” or “Critical” are defined by an administrator, and if users choose non-default language on their properties, the different definitions are shown on the local help.
The symptom doesn’t occurred if users choose the default language.
If priority names are other than “Blocker” or “Critical”, definitions are shown as expected.
Replicated on 9.4.2, 9.4.23 and 9.16.1.

Steps to Reproduce

1. Navigate to [Gear] icon > “System”. Make sure that the Default language is “English”. If not, select “English” as the default language.
2. Navigate to [Gear] icon > “Issues”. Then select “Priorities” on the side menu
3. Click “Add priority” button and add those priorities
   Name: Blocker
   Description: Blocker
   Icon URL: /images/icons/priorities/blocker.svg
   Color: #ffffff

Name: Critical
Description: Critical
Icon URL: /images/icons/priorities/critical.svg
Color: #ffffff

1. Open “Profile”, then select non-default language (ex. “English (UK)) as the “Language” value in “Preferences” section
2. Navigate to [Gear] icon > “Issues”. Then select “Priorities” on the side menu again and make sure definitions of “Blocker” and “Critical” are the same as above setting
3. Click “Create” button, then scroll down to “Priority” and click [?] icon at the end of the line
4. The local help will be opened on another tab on the browser. Check definitions of “Blocker” and Critical” priorities

Expected Results

Definitions of “Blocker” and “Critical” priorities in the local help for non-default language are the same as the original setting.

Actual Results

For non-default language, definitions of “Blocker” and “Critical” became the following sentence (or the translation to the local language).
Blocker: Blocks development and/or testing work, production could not run.
Critical: Crashes, loss of data, severe memory leak.

Workaround

The workaround is to add translations to those priorities by using “Translate priorities”.