Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30323

Cannot translate new issue navigator.

XMLWordPrintable

      Hi,

      Now I'm evaluating JIRA 5.2 EAP version, it is an important feedback.

      I can't translate new basic issue navigator page and its popup dialog, due to the difference between Japanese and English grammar rules.
      That part are entries of prefix "navigator.filter.date." and "popups." in TAC. Please see my attached screenshot.

      Best regards,
      Kan Ogawa

        1. BasicIssueNavigator_DateTypeClause.png
          BasicIssueNavigator_DateTypeClause.png
          53 kB
        2. BasicIssueNavigator.png
          BasicIssueNavigator.png
          46 kB
        3. CreatedDate_Criteria.png
          CreatedDate_Criteria.png
          35 kB
        4. ResolvedDate_Criteria.png
          ResolvedDate_Criteria.png
          35 kB
        5. Screen Shot 2012-11-07 at 5.38.11 PM.png
          Screen Shot 2012-11-07 at 5.38.11 PM.png
          17 kB
        6. Screen Shot 2012-11-07 at 5.38.48 PM.png
          Screen Shot 2012-11-07 at 5.38.48 PM.png
          15 kB

            [JRASERVER-30323] Cannot translate new issue navigator.

            Kan Ogawa added a comment -

            Hi Eric,

            The issue for the display text and tooltip (navigator.filter.*) is a larger change and appears to be similar to pre-5.2 behaviour. The way to construct the key using keys such as navigator.filter.duedate.after, navigator.hidden.search.request.summary.date.ago is essentially pre-5.2 behvaiour. I agree that it should be fixed however it is not possible for 5.2.1; I have created JRA-30513 to track.

            I have commented my proposal about i18n keys in JRA-30513 issue.

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi Eric, The issue for the display text and tooltip (navigator.filter.*) is a larger change and appears to be similar to pre-5.2 behaviour. The way to construct the key using keys such as navigator.filter.duedate.after, navigator.hidden.search.request.summary.date.ago is essentially pre-5.2 behvaiour. I agree that it should be fixed however it is not possible for 5.2.1; I have created JRA-30513 to track. I have commented my proposal about i18n keys in JRA-30513 issue. Best regards, Kan Ogawa

            Kan Ogawa added a comment - - edited

            Hi Eric,

            Now I continue to validate this localization issue for issue navigator.
            I have provided additional feedback to JRA-30748.

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - - edited Hi Eric, Now I continue to validate this localization issue for issue navigator. I have provided additional feedback to JRA-30748 . Best regards, Kan Ogawa

            Eric Dalgliesh added a comment -

            Thanks Kan! I'm not sure how we missed that. We'll sort it out.

            Eric Dalgliesh added a comment - Thanks Kan! I'm not sure how we missed that. We'll sort it out.

            Kan Ogawa added a comment -

            Hi Eric,

            Translations data for JIRA 5.2.1 aren't uploaded in TAC yet.
            When they will be uploaded?

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi Eric, Translations data for JIRA 5.2.1 aren't uploaded in TAC yet. When they will be uploaded? Best regards, Kan Ogawa

            Kan Ogawa added a comment -

            Hi,

            Both criteria 'Created Date' and 'Resolved Date' for issue are different from each field name. These need to be fixed.

            I have created new ticket JRA-30748.

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi, Both criteria 'Created Date' and 'Resolved Date' for issue are different from each field name. These need to be fixed. I have created new ticket JRA-30748 . Best regards, Kan Ogawa

            Kan Ogawa added a comment -

            Hi Jonathon,

            I have attached two screenshots.
            Both criteria 'Created Date' and 'Resolved Date' for issue are different from each field name. These need to be fixed.

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi Jonathon, I have attached two screenshots. Both criteria 'Created Date' and 'Resolved Date' for issue are different from each field name. These need to be fixed. Best regards, Kan Ogawa

            Kan Ogawa added a comment -

            Hi Jonathon,

            Thanks for your support!

            Currently, Japanese participants with me are discussing about the issue for the date searcher bar strings (navigator.filter.*).
            If improvement points have been summarized, we will feedback into JRA-30513 issue.

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi Jonathon, Thanks for your support! Currently, Japanese participants with me are discussing about the issue for the date searcher bar strings (navigator.filter.*). If improvement points have been summarized, we will feedback into JRA-30513 issue. Best regards, Kan Ogawa

            Jonathon Creenaune added a comment -

            Kan, I have committed a fix for the searcher popup keys (popups.daterange.*) that will be released in 5.2.1. This was a clear breakage in 5.2.

            The issue for the display text and tooltip (navigator.filter.*) is a larger change and appears to be similar to pre-5.2 behaviour. The way to construct the key using keys such as navigator.filter.duedate.after, navigator.hidden.search.request.summary.date.ago is essentially pre-5.2 behvaiour. I agree that it should be fixed however it is not possible for 5.2.1; I have created JRA-30513 to track.

            Jonathon Creenaune added a comment - Kan, I have committed a fix for the searcher popup keys (popups.daterange.*) that will be released in 5.2.1. This was a clear breakage in 5.2. The issue for the display text and tooltip (navigator.filter.*) is a larger change and appears to be similar to pre-5.2 behaviour. The way to construct the key using keys such as navigator.filter.duedate.after, navigator.hidden.search.request.summary.date.ago is essentially pre-5.2 behvaiour. I agree that it should be fixed however it is not possible for 5.2.1; I have created JRA-30513 to track.

            Kan Ogawa added a comment -

            Hi Jonathon,

            Your attached screenshots are current UI design.
            Until they are improved, it is difficult to translate into Japanese language.

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi Jonathon, Your attached screenshots are current UI design. Until they are improved, it is difficult to translate into Japanese language. Best regards, Kan Ogawa

            Mairead (Inactive) added a comment -

            Thanks for the feedback. We're investigating the issue and hoping to get a fix out as soon as possible. More details to follow shortly

            Mairead
            Product Manager JIRA

            Mairead (Inactive) added a comment - Thanks for the feedback. We're investigating the issue and hoping to get a fix out as soon as possible. More details to follow shortly Mairead Product Manager JIRA

              edalgliesh Eric Dalgliesh
              f9ced3a62372 Kan Ogawa
              Affected customers:
              2 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: