Some strings are customised more than once. For coluimns name see the COLUMN_ keys.

Which key does not work?

Oh, I didn't rename the keys because I didn't want to modify every reference to them in every file so I thought I could just modify the values in the XMLs.  I was just wondering if there was an easy way to have the values that show up in customise use the values and not the keys.

Sorry, you did not understand me.

We are using the values of the key:

<item name="COLUMNIssueID">Issue ID</item>

 <item name="COLUMNIssueID">Issue Identifier</item>

I also noticed that Update emails show the field keys instead of the values.

The following fields I have modified and do not show properly in customise or emails:

 <item name="COLUMNIssuePriority">Severity</item>
 <item name="COLUMNIssuePrioritySequence" toTranslate="TRUE">Severity Sequence</item>
 <item name="COLUMNIssuePriorityDesc">Severity</item>
 <item name="COLUMNRiskLevel">Priority</item>
 <item name="COLUMNRiskLevelDesc">Priority</item>
 <item name="COLUMNStartDate">Estimated Release Date</item>

These show up properly on the list view just not in the customise screen (user/IssuesView.aspx?PROJID=-2) under the Available Issue Properties and Selected Issue Properties select fields.

They show as IssuePriority, IssuePriorityDesc, RiskLevel, RiskLevelDesc and StartDate.

Example snippet or email:

Field Previous Value Current Value Priority Low Medium

Priority should read Severity.

I see, the customise screen can not be customised at the moment.

We will look into making this possible for the next releas: http://gemini.countersoft.com/Default.aspx?p=2&i=1200

Emails, unfortunately, can be customised to one language only. See the templates directory.