[Building Sakai] Suggestion for improvement of i18n and L10n handling in JIRA

[Jean-Francois Leveque]

All the CLE internationalization component issues are currently 
automagically assigned to Beth Kirschner (Lead for this component in 
JIRA) if the real component name is after Internationalization in 
alphabetical order. She then assigns most of the issues to the real 
component owner. I don't think this is really convenient.

Internationalization and translation issues are currently mixed in the 
internationalization component. There is no way to know the ones are 
internationalization from the ones that are translation.

A better solution for both issues is welcome if my suggestion is not 
good enough.

J-F

On 31/01/2012 17:35, Aaron Zeckoski wrote:
> That doesn't really sound easier to me and there are getting to be an
> awful lot of checkboxes there. The current filters should do exactly
> what you want without a lot of work to make this change in JIRA.
> -AZ
>
>
> On Tue, Jan 31, 2012 at 11:01 AM, Jean-Francois Leveque
> <jean-francois.leveque at upmc.fr>  wrote:
>> Hi
>>
>> Currently, SAK issues can have internationalization in the list of
>> components.
>>
>> AFAICT, the only real internationalization component has been in kernel
>> since the creation of kernel with Sakai 2.6.0.
>>
>> Currently the JIRA internationalization component is used both for L10n
>> and i18n issues.
>>
>> I suggest we stop using this component and add 2 new check-boxes (like
>> the Maintenance Team Issue one):
>> Internationalization Issue
>> Localization Issue
>>
>> It seems to me this way will be easier to check which languages have
>> been updated or to look for internationalization issues.
>>
>> What do you think ?
>>
>> Cheers,
>>
>> J-F