Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.4.4, 5.5-OD-28, 5.10.4, 6.1.2, 6.1.3, 6.4.3, 7.4.9, 7.19.0
-
21
-
Severity 3 - Minor
-
4
-
Description
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
- Create a custom field in JIRA.
- Translate custom field into another language (language B)
- Change JIRA language to language B
- Ensure Confluence is in language A.
- Insert JIRA issues macro and adjust display options to ensure it will include custom field.
- Custom field will display in language B, the other fields in language A, matching Confluence's profile language.
- Change JIRA back to language A.
- Check Confluence, custom field is still in language B.
- Edit page, re-insert JIRA issues macro, and language will now be in language A.
- Change Confluence to language B, custom field is still in language A
- The Jira filters macro does not load the value from the custom field.
Tested in English/Japanese, and it's reported also in English/German
Attachments
Issue Links
- is duplicated by
-
CONFSERVER-57718 Custom fields not displayed in Jira issue macro when changing the language
- Long Term Backlog
- is related to
-
JRASERVER-38965 Unable to create issue from Confluence if they have different languages due to priority translation
- Gathering Impact
- relates to
-
I18N-2876 Translations for Custom JIRA Fields in Issues Macro do not match Confluence Language
- Closed
-
CONFSERVER-79885 Custom field with translation doesn't display value if user profile language on Jira and Confluence is different
- Gathering Impact
- mentioned in
-
Page Loading...