MantisBT

View Issue Details Jump to Notes ] Wiki ] Related Changesets ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0012470mantisbtcustom fieldspublic2010-10-22 04:532014-02-07 18:24
Reporterjmonin 
Assigned Todregad 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.2.3 
Target Version1.2.16Fixed in Version1.2.16 
Summary0012470: Custom fields names aren't translated in several places
DescriptionCustom fields are displayed with their name, disregarding their localization :
- in the history log
- in the custom fields section, in the project management page
TagsNo tags attached.
Attached Filespatch file icon mantis-1.2.3-patch-custom-translation-history.patch [^] (430 bytes) 2010-10-22 04:53 [Show Content]
patch file icon mantis-1.2.3-patch-custom-translation-manage-project.patch [^] (874 bytes) 2010-10-22 04:53 [Show Content]

- Relationships
has duplicate 0016335closedatrol Localized custom field names in bug history 

-  Notes
User avatar (0027118)
jmonin (reporter)
2010-10-22 04:54

You'll find attached the patches I made on my Mantis 1.2.3 deployment here.
User avatar (0037945)
dregad (developer)
2013-08-28 19:39

Comment from grangeway:

I think this may have been deliberate - it's feasible to add 2 custom fields that localise to 1 string. You now can't identify which custom field is which.
User avatar (0037946)
zrybola (reporter)
2013-08-29 02:23

@dregad: I don't believe this is really an issue in the bug history. If multiple custom fields localise to the same string you can't distinguish them in the bug report form or bug detail page either. Therefore we can suppose that custom fields in the same project have different localized names. However, in the custom field management page there should be the original name along with the localized string to help with the identification.
User avatar (0037948)
dregad (developer)
2013-08-29 05:35

Yep. Exactly what I said: http://article.gmane.org/gmane.comp.bug-tracking.mantis.devel/4525 [^]

- Related Changesets
MantisBT: master-1.2.x c174d88f
Timestamp: 2013-08-28 11:46:40
Author: dregad
Details ] Diff ]
Translate custom field names

Custom fields are displayed with their name, disregarding their
localization :
- in the history log
- in the custom fields section, in the project management page

Thanks to jmonin for the patch.

Fixes 0012470
mod - core/history_api.php Diff ] File ]
mod - manage_proj_edit_page.php Diff ] File ]
MantisBT: master 65835d64
Timestamp: 2013-08-28 11:46:40
Author: dregad
Details ] Diff ]
Translate custom field names

Custom fields are displayed with their name, disregarding their
localization :
- in the history log
- in the custom fields section, in the project management page

Thanks to jmonin for the patch.

Fixes 0012470

Conflicts:
    manage_proj_edit_page.php
mod - core/history_api.php Diff ] File ]
mod - manage_proj_edit_page.php Diff ] File ]
MantisBT: master-1.2.x 9b9c2cc4
Timestamp: 2013-08-29 11:06:25
Author: dregad
Details ] Diff ]
Follow-up fix for custom field names translations

In the case where we have multiple custom strings localized to the same
string, commit c174d88fc4f6a92e5bff0f7660688f1757c4cdaf would make it
impossible to distinguish them.

While this should not be a major issue in the bug history (as it doesn't
make sense to have more than one fields with a given localized name
within a given project), it is important that in custom field management
as well as project management pages custom fields are uniquely
identified with their "system" name to ensure there is no confusion.

This commit adds a new API function custom_field_get_display_name() that
will append the localized name to the field name, and which is called
from the above-mentioned pages.

Issue 0012470
mod - core/custom_field_api.php Diff ] File ]
mod - manage_custom_field_page.php Diff ] File ]
mod - manage_proj_edit_page.php Diff ] File ]
MantisBT: master d45881d8
Timestamp: 2013-08-29 11:06:25
Author: dregad
Details ] Diff ]
Follow-up fix for custom field names translations

In the case where we have multiple custom strings localized to the same
string, commit c174d88fc4f6a92e5bff0f7660688f1757c4cdaf would make it
impossible to distinguish them.

While this should not be a major issue in the bug history (as it doesn't
make sense to have more than one fields with a given localized name
within a given project), it is important that in custom field management
as well as project management pages custom fields are uniquely
identified with their "system" name to ensure there is no confusion.

This commit adds a new API function custom_field_get_display_name() that
will append the localized name to the field name, and which is called
from the above-mentioned pages.

Issue 0012470

Conflicts:
    manage_proj_edit_page.php
mod - core/custom_field_api.php Diff ] File ]
mod - manage_custom_field_page.php Diff ] File ]
mod - manage_proj_edit_page.php Diff ] File ]

- Issue History
Date Modified Username Field Change
2010-10-22 04:53 jmonin New Issue
2010-10-22 04:53 jmonin File Added: mantis-1.2.3-patch-custom-translation-history.patch
2010-10-22 04:53 jmonin File Added: mantis-1.2.3-patch-custom-translation-manage-project.patch
2010-10-22 04:54 jmonin Note Added: 0027118
2013-08-28 05:44 atrol Relationship added has duplicate 0016335
2013-08-28 11:48 dregad Changeset attached => MantisBT master-1.2.x c174d88f
2013-08-28 11:48 dregad Assigned To => dregad
2013-08-28 11:48 dregad Status new => resolved
2013-08-28 11:48 dregad Resolution open => fixed
2013-08-28 11:48 dregad Fixed in Version => 1.2.16
2013-08-28 11:50 dregad Changeset attached => MantisBT master 65835d64
2013-08-28 11:50 dregad Target Version => 1.2.16
2013-08-28 19:39 dregad Note Added: 0037945
2013-08-29 02:23 zrybola Note Added: 0037946
2013-08-29 05:35 dregad Note Added: 0037948
2013-08-30 12:35 dregad Changeset attached => MantisBT master-1.2.x 9b9c2cc4
2013-08-30 12:35 dregad Changeset attached => MantisBT master d45881d8
2014-02-07 18:24 dregad Status resolved => closed


MantisBT 1.2.17 [^]
Copyright © 2000 - 2014 MantisBT Team
Time: 0.1072 seconds.
memory usage: 3,063 KB
Powered by Mantis Bugtracker