Work Item Template Import issue
We're going to use WorkItem Templates but we found a limitation regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their names (Summary field).
When we use the "Import Work Item Template" feature, the xml content is changed and accentuation characters are converted. Submitting new work items from this template, the converted words aren't decoded to the original state.
This is an issue for our solution because we're planning to share work item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
A lot of pre-defined tasks of our process have accentuation in their names (Summary field).
When we use the "Import Work Item Template" feature, the xml content is changed and accentuation characters are converted. Submitting new work items from this template, the converted words aren't decoded to the original state.
This is an issue for our solution because we're planning to share work item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
6 answers
We're going to use WorkItem Templates but we found a limitation regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their names (Summary field).
When we use the "Import Work Item Template" feature, the xml content is changed and accentuation characters are converted. Submitting new work items from this template, the converted words aren't decoded to the original state.
This is an issue for our solution because we're planning to share work item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
Raise it as a defect anyway.
Did you make sure the language/charset/keyboard settings are the same on the different systems?
anthony
We're going to use WorkItem Templates but we found a limitation regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their names (Summary field).
When we use the "Import Work Item Template" feature, the xml content is changed and accentuation characters are converted. Submitting new work items from this template, the converted words aren't decoded to the original state.
This is an issue for our solution because we're planning to share work item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
Raise it as a defect anyway.
Did you make sure the language/charset/keyboard settings are the same on the different systems?
anthony
The unexpected behavior occurs with work item templates created and used in the same system. It is realized both in English language setting or Brazilian Portuguese.
Defect raised: http://jazz.net/jazz/web/projects/Rational Team Concert#action=com.ibm.team.workitem.viewWorkItem&id=109673
Thanks Anthony.
Regards,
Adriano Ramos
On Mon, 22 Mar 2010 18:08:00 +0100, nofarias
<nofarias> wrote:
Hi there,
characters used in workitem templates are assumed to be encoded with
UTF-8. Characters may be converted if a different encoding is used. If
your template files are encoded with UTF-8 and characters are still
converted, I'd consider it a bug. Can you provide a template as a file
attachment?
Thanks,
Jan.
--
Jan Wloka
Jazz Planning & Tracking Team
<nofarias> wrote:
Hi there,
characters used in workitem templates are assumed to be encoded with
UTF-8. Characters may be converted if a different encoding is used. If
your template files are encoded with UTF-8 and characters are still
converted, I'd consider it a bug. Can you provide a template as a file
attachment?
Thanks,
Jan.
--
Jan Wloka
Jazz Planning & Tracking Team
We're going to use WorkItem Templates but we found a limitation
regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their
names (Summary field).
When we use the "Import Work Item Template" feature, the xml
content is changed and accentuation characters are converted.
Submitting new work items from this template, the converted words
aren't decoded to the original state.
This is an issue for our solution because we're planning to share work
item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
We're going to use WorkItem Templates but we found a limitation
regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their
names (Summary field).
When we use the "Import Work Item Template" feature, the xml
content is changed and accentuation characters are converted.
Submitting new work items from this template, the converted words
aren't decoded to the original state.
This is an issue for our solution because we're planning to share work
item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
You are probably seeing
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/103003
This was fixed for 3.0 but is still present in 2.0.0.2.
You could try the workaround mentioned in comment 4 of the work item:
Modify eclipse.ini to include
-Dfile.encoding=UTF-8
--
Regards,
Patrick
Jazz Work Item Team
We're going to use WorkItem Templates but we found a limitation
regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their
names (Summary field).
When we use the "Import Work Item Template" feature, the xml
content is changed and accentuation characters are converted.
Submitting new work items from this template, the converted words
aren't decoded to the original state.
This is an issue for our solution because we're planning to share work
item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1
You are probably seeing
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/103003
This was fixed for 3.0 but is still present in 2.0.0.2.
You could try the workaround mentioned in comment 4 of the work item:
Modify eclipse.ini to include
-Dfile.encoding=UTF-8
--
Regards,
Patrick
Jazz Work Item Team
Hi Patrick,
the workaround solved the problem! Now WIs are submitted with correct characters.
Thanks!
Adriano Ramos
Hi Jan,
I attached 2 files as example of the problem in the defect #109673
Regards.
Adriano Ramos.
I attached 2 files as example of the problem in the defect #109673
Regards.
Adriano Ramos.
On Mon, 22 Mar 2010 18:08:00 +0100, nofarias
<nofarias> wrote:
Hi there,
characters used in workitem templates are assumed to be encoded with
UTF-8. Characters may be converted if a different encoding is used. If
your template files are encoded with UTF-8 and characters are still
converted, I'd consider it a bug. Can you provide a template as a file
attachment?
Thanks,
Jan.
--
Jan Wloka
Jazz Planning & Tracking Team
We're going to use WorkItem Templates but we found a limitation
regarding special characters (accentuation).
A lot of pre-defined tasks of our process have accentuation in their
names (Summary field).
When we use the "Import Work Item Template" feature, the xml
content is changed and accentuation characters are converted.
Submitting new work items from this template, the converted words
aren't decoded to the original state.
This is an issue for our solution because we're planning to share work
item templates between Project Areas.
Can we consider a bug?
RTC version is 2.0.0.2iFix1