Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-77291

Jira Issues Macro to display content in Confluence's user set language instead of Jira’s default language

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Macros - Jira Macros
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue Summary

      Requesting that the Jira Issues Macro (JIM) display user generaged content in Confluence's user set language instead of Jira’s default language. Since the fix of CONFSERVER-42863 the Jira Issues Macro works per the following:

      • The JIM issue contents (eg: Open) are in Jira’s default language
      • The JIM table headers (eg: Status) are in Confluence user’s preferred language
      • Any date type fields rendered in JIM are in Confluence user’s time zone
      • Any date type fields rendered in JIM are in Confluence user’s preferred language

      The outlier is that the JIM issue contents display in Jira's default language instead of the Confluence uer's preferred language. It's possible to translate resolutions, priorities, statuses, and issue types so having these translations appear in the Confluence user's preferred language when viewing in JIM should be possible.

      Steps to Reproduce

      1. Set the Jira’s default language different from the Confluence user’s preferred language:
        1. Log in as an admin user
        2. Click on the property gear in the top right corner and select 'System'
        3. Click 'Edit settings'
        4. Scroll to 'Default language' line and select a language other than the Confluence user's preferred language, for example 'Deutsch'
      2. Create a new task in Jira. 
      3. Create a new page in Confluence and add Jira Issues Macro (JIM) there:
        1. Click '+' in menu toolbar and select 'Jira Issue/Filter'
        2. Search by issue key your issue
        3. Expand 'Display options'
        4. Set 'Display as' as 'Table'
        5. Click 'Insert' and 'Publish'

      Expected Results

      When viewing resolutions, priorities, statuses, and issue types in JIM they will adopt the Confluence User's default language.

      Actual Results

      When viewing resolutions, priorities, statuses, and issue types in JIM they the use Jira's default language.

      Workaround

      Currently there is no known workaround for this behaviour. A workaround will be added here when available

      Notes

      It is possible to specify a translated name and description for resolutions, priorities, statuses, and issue types - link to the documentation (please check the attached screen recordings)
      For example, if the default Jira language is English and you create a new status called 'Cat', then the following will happen:

      1. Jira default language = English. It’s simple. JIM will display 'Cat' on the Confluence page
      2. Jira default language = not English:
        1. If we don’t add a translation to the combination status + language, then the new status will be displayed as 'Cat' in the Jira issue and on the Confluence page.
        2. If we add a translation to the combination status + language ('猫'), then the new status will be displayed as '猫' in the Jira issue and on the Confluence page.

      To change Status display name:

      1. Log in as an admin user
      2. Click on the property gear in the top right corner and select 'Issues'
      3. In the menu on the left, select the 'Statuses' menu item
      4. Click 'Translate statuses', select the desired language, provide a translation, and click 'Update'

       

        1. part2.mov
          26.41 MB
          Anna-Mariia Chyzhevska
        2. part1.mov
          49.93 MB
          Anna-Mariia Chyzhevska

              Unassigned Unassigned
              cee80e86d823 Anna-Mariia Chyzhevska (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: