|
Hi Mel,
I am always waiting for a return, too ! Vincent Is it possible to have a return for this issue ?
Rgds Vincent It is quite important indeed, some feedback would be appreciated.
Regards Mel Sorry guys,
No news on this one yet. We haven't scheduled it yet but will update when we do. Sorry I can't provide a more definitive answer. Cheers, Are there any plans to implement this feature at all?
Regards Mel Hi Nick and Atlassian guys,
I suppose that I18n for Customfield is not yet scheduled, but my initial request was not only if the requirement of this new feature. I am also interesting to know if my proposed solution is acceptable and will not go against your future solution. In my company, we are about to deploy JIRA for more that 3000 users with French, English and Italian people. Thanks per advance. Sorry Vincent,
Been on holidays. The main problem with i18n of custom fields is that the custom field names are configurable at run time and hence the translations will not be stored in property files, more likely the database. That being said, your method should not go against our solution. I.e. you should require little change to make it compatible. (though it is hard to say before implementing the solution) Cheers, I just wanted to add my voice in favor of a permanent solution for this problem (I've already added my vote). It came as a suprise to me that this wasn't supported, but I understand the technical stumbling blocks behind this.
I wonder how many people think that "internationalized jira" includes "custom fields" ... ? For the record, I've implemented Vincent's method in my copy of 3.10.2 and it works like a charm. Merci infiniment Vincent. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Is there any update on this issue?
MB