-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
5.2
-
5.02
-
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
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
JRADEV-18229 Failed to load
-
JRADEV-18232 Failed to load
-
JRADEV-18233 Loading...
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-30323] Cannot translate new issue navigator.
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 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 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 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
Hi Eric,
I have commented my proposal about i18n keys in
JRA-30513issue.Best regards,
Kan Ogawa