Issue Summary

When the site’s default language is English (US), a user whose personal language is set to a language other than English, such as Japanese, sees localized work types such as バグ, タスク, and ストーリー as available options when adding work types to a team-managed space.

When one of these work types is added, it is created as a separate work type from the existing English work type. As a result, the same team-managed space can contain English and Japanese work types with different IDs, even though they have the same meaning.

For example:

• Bug (ID: 10120)

• バグ (ID: 10121)

This can cause confusion when identifying and managing work types.

Steps to Reproduce

1. Set the Jira Cloud site’s default language to English (US).
2. Set the operating user’s personal language to Japanese.
3. Create a team-managed software space.
4. After creating the space, confirm that the following default work types exist:
   Epic
   Feature
   Story
   Bug
   Task
5. Open Work types in the space settings.
6. Click Add work type.
7. Review the available work type options.
8. Select and add the Japanese work type バグ.
9. Review the list of work types in the space.
10. Compare the IDs of the existing Bug work type and the newly added バグ work type.

Expected Results

• When a standard work type already exists, the existing work type should be reused regardless of the operating user’s personal language setting.

• Localized versions of existing work types should not be displayed as separate work types that can be added.

Actual Results

• Although the site’s default language is English, a user whose personal language is Japanese sees Japanese work types as options under Add work type.

• When バグ is added, a separate work type is created instead of reusing the existing Bug work type.

• As a result, Bug and バグ exist as separate work types with different IDs in the same space.

Workaround

To prevent duplicate work types from being created, set the operating user’s personal language to the same language as the site’s default language before adding a work type.

If duplicate work types have already been created, an administrator can manually delete the unnecessary work type after confirming that:

• No issues are associated with the work type; and

• Deleting it will not affect the operation of the space.