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

Field names of 'Created Date' and 'Resolution Date' in issue nav are incorrect.

      Hi,

      This is JRA-30323 regression.
      Both criteria 'Created Date' (作成日) and 'Resolution Date' (解決日) for issue navigator popup window are different from each field name. These need to be fixed too.
      (See my attached screenshots)

      Best regards,
      Kan Ogawa

        1. CreatedDate_Criteria.png
          CreatedDate_Criteria.png
          35 kB
        2. dates new i18n strings.jpg
          dates new i18n strings.jpg
          400 kB
        3. date strings en.jpg
          date strings en.jpg
          88 kB
        4. date strings jp.jpg
          date strings jp.jpg
          58 kB
        5. fixed created date.jpg
          fixed created date.jpg
          106 kB
        6. fixed resolution date.jpg
          fixed resolution date.jpg
          104 kB
        7. ResolvedDate_Criteria.png
          ResolvedDate_Criteria.png
          35 kB

            [JRASERVER-30748] Field names of 'Created Date' and 'Resolution Date' in issue nav are incorrect.

            Fixed in JIRA 5.2.11.

            Luis Miranda (Inactive) added a comment - Fixed in JIRA 5.2.11.

            The "In range..." message is unchanged. JRA-30513 has also been addressed, please see my comment on that issue.

            Luis Miranda (Inactive) added a comment - The "In range..." message is unchanged. JRA-30513 has also been addressed, please see my comment on that issue.

            Kan Ogawa added a comment -

            Hi Luis,

            Sorry. I have reviewed the changes again.

            Original I18N String Can translate?
            Within the last {0} {1} OK
            More than {0} {1} ago OK
            Between {0} and {1} OK
            In range {0} to {1} Newly defined? or Unchanged?

            BTW, are you defining I18N original strings in Instant Search Bar additionally? (JRA-30513)
            Examples - Instant Search Bar text/tooltip

            navigator.filter.daterange.withinthelast = Within the last {0} {1}
            navigator.filter.daterange.morethanago = More than {0} {1} ago
            navigator.filter.daterange.datebetween = {0} and {1}
            navigator.filter.daterange.inrange = From {0} from now to {1} from now
            

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi Luis, Sorry. I have reviewed the changes again. Original I18N String Can translate? Within the last {0} {1} OK More than {0} {1} ago OK Between {0} and {1} OK In range {0} to {1} Newly defined? or Unchanged? BTW, are you defining I18N original strings in Instant Search Bar additionally? ( JRA-30513 ) Examples - Instant Search Bar text/tooltip navigator.filter.daterange.withinthelast = Within the last {0} {1} navigator.filter.daterange.morethanago = More than {0} {1} ago navigator.filter.daterange.datebetween = {0} and {1} navigator.filter.daterange.inrange = From {0} from now to {1} from now Best regards, Kan Ogawa

            ogawa@ricksoft.jp unfortunately the above text did not read well in English. So I am defining 3 new strings, which you should be able to translate in Japanese. They are:

            popups.daterange.withinthelast = Within the last {0} {1}
            popups.daterange.morethanago = More than {0} {1} ago
            popups.daterange.datebetween = Between {0} and {1}
            

            The field name/verb is no longer present in the pop-up so it will be easier to translate (this string is not used elsewhere) and works equally well. Example:

            English

            Japanese

            Luis Miranda (Inactive) added a comment - ogawa@ricksoft.jp unfortunately the above text did not read well in English. So I am defining 3 new strings, which you should be able to translate in Japanese. They are: popups.daterange.withinthelast = Within the last {0} {1} popups.daterange.morethanago = More than {0} {1} ago popups.daterange.datebetween = Between {0} and {1} The field name/verb is no longer present in the pop-up so it will be easier to translate (this string is not used elsewhere) and works equally well. Example: English Japanese

            Kan Ogawa added a comment -

            Thanks Luis!

            I have verified your changes.

            Field Japanese translation review
            Created OK
            Resolved OK

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Thanks Luis! I have verified your changes. Field Japanese translation review Created OK Resolved OK Best regards, Kan Ogawa

            ogawa@ricksoft.jp I've applied the changes you suggested. Can you verify that this translates correctly in Japanese?

            Created

            Resolved

            Luis Miranda (Inactive) added a comment - ogawa@ricksoft.jp I've applied the changes you suggested. Can you verify that this translates correctly in Japanese? Created Resolved

            Thanks Kan! It's too late for these changes to make 5.2.2 but we'll try to get them into a release soon after that.

            Eric Dalgliesh added a comment - Thanks Kan! It's too late for these changes to make 5.2.2 but we'll try to get them into a release soon after that.

            Kan Ogawa added a comment -

            Hi,

            I have found the cause of this problem using JIRA IPT plugin.

            I18N keys for both fields are unsuitable.
            It should avoid using the texts together in other pages.

            Field name (Original text in TAC) Entry key in TAC
            Created gadget.recently.created.issues.created
            Resolved common.concepts.resolved⁠

            I think that i18n keys for popup window in issue navigator should be modified.
            The following keys in TAC are appropriate:

            Field name (Original text in TAC) Entry key in TAC
            Created Date navigator.filter.created
            Resolution Date navigator.filter.resolutiondate

            Best regards,
            Kan Ogawa

            Kan Ogawa added a comment - Hi, I have found the cause of this problem using JIRA IPT plugin. I18N keys for both fields are unsuitable. It should avoid using the texts together in other pages. Field name (Original text in TAC) Entry key in TAC Created gadget.recently.created.issues.created Resolved common.concepts.resolved⁠ I think that i18n keys for popup window in issue navigator should be modified. The following keys in TAC are appropriate: Field name (Original text in TAC) Entry key in TAC Created Date navigator.filter.created Resolution Date navigator.filter.resolutiondate Best regards, Kan Ogawa

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

                Created:
                Updated:
                Resolved: