It's all about the answers!

Ask a question

Custom import XML


Kevin Ramer (4.5k8183200) | asked Oct 14 '08, 3:44 p.m.
Hello,

I've been battling Bugzilla imports and I'm trying to take a generated
mapping file and add 1 additional attribute. That looks like
this in the RTC repository (configuration xml)



<customAttributes>
<customAttribute>
</customAttributes>

I added this to a generated mapping xml:

<attribute>

And my bug source files look like:

<xml>
<bugzilla>
<bug>
<bug_id>24518</bug_id>
<creation_ts>2008-05-27 06:18:58</creation_ts>
<reporter>kxxxxxx@us.ibm.com</reporter>
<short_desc>We Couldn't Login in CMDB-DM while Creating usergroups withAd..</short_desc>
<delta_ts>2008-10-01 14:56:14</delta_ts>
<component>cmdb.ecmdb</component>
<prefix>p</prefix>
<bug_status>NEW</bug_status>
<bug_resolution></bug_resolution>
<bug_severity>High</bug_severity>
<assigned_to>jxxxxxxx@us.ibm.com</assigned_to>
....
</bug></bugzilla>

Import doesn't pick up the value 'p' in the file.

Am I reading all the docs wrong ? Is the bugzilla importer fixed in what
fields it's willing to import ?



--
Kevin Ramer ramerk@us.ibm.com
Tivoli Advisory Software Engineer

7 answers



permanent link
Lorelei Ngooi (1.5k22) | answered Oct 16 '08, 4:01 p.m.
JAZZ DEVELOPER
Hi Kevin,

If I understand you correctly, you have created a custom attribute in the process spec and have modified the generated data mapping file to map the Bugzilla prefix field to this custom attribute. Your custom attribute should look something like this in the process spec:

<customAttributes category="com.ibm.team.workitem.workItemType">
<customAttribute id="com.ibm.workitem.attribute.custom.prefix" name="Prefix" type="smallString"/>
</customAttributes>

Then in the generated mapping file, there should be an entry like this:
<attribute sourceId="prefix" targetId="com.ibm.workitem.attribute.custom.prefix">
</attribute>

Lorelei
Jazz CQ Connector Team

Hello,

I've been battling Bugzilla imports and I'm trying to take a generated
mapping file and add 1 additional attribute. That looks like
this in the RTC repository (configuration xml)



<customAttributes>
<customAttribute>
</customAttributes>

I added this to a generated mapping xml:

<attribute>

And my bug source files look like:

<xml>
<bugzilla>
<bug>
<bug_id>24518</bug_id>
<creation_ts>2008-05-27 06:18:58</creation_ts>
<reporter>kxxxxxx@us.ibm.com</reporter>
<short_desc>We Couldn't Login in CMDB-DM while Creating usergroups withAd..</short_desc>
<delta_ts>2008-10-01 14:56:14</delta_ts>
<component>cmdb.ecmdb</component>
<prefix>p</prefix>
<bug_status>NEW</bug_status>
<bug_resolution></bug_resolution>
<bug_severity>High</bug_severity>
<assigned_to>jxxxxxxx@us.ibm.com</assigned_to>
....
</bug></bugzilla>

Import doesn't pick up the value 'p' in the file.

Am I reading all the docs wrong ? Is the bugzilla importer fixed in what
fields it's willing to import ?



--
Kevin Ramer ramerk@us.ibm.com
Tivoli Advisory Software Engineer

permanent link
Kevin Ramer (4.5k8183200) | answered Oct 17 '08, 7:06 a.m.
But when I open the project configuration I see this:


<customAttribute id="prefix" name="Prefix" type="smallString"/>




Thus it is not named com.ibm.team.workitem.anything.

I did find a enhancement yesterday in Jazz repository with a patch jar to fix some
issues with imports and 'non-standard' fields. Not being an Eclipse Guru I couldn't
get the fix to have any effect.

Hi Kevin,

If I understand you correctly, you have created a custom attribute in the process spec and have modified the generated data mapping file to map the Bugzilla prefix field to this custom attribute. Your custom attribute should look something like this in the process spec:

<customAttributes>
<customAttribute>
</customAttributes>

Then in the generated mapping file, there should be an entry like this:
<attribute>
</attribute>

Lorelei
Jazz CQ Connector Team

Hello,

I've been battling Bugzilla imports and I'm trying to take a generated
mapping file and add 1 additional attribute. That looks like
this in the RTC repository (configuration xml)



<customAttributes>
<customAttribute>
</customAttributes>

I added this to a generated mapping xml:

<attribute>

And my bug source files look like:

<xml>
<bugzilla>
<bug>
<bug_id>24518</bug_id>
<creation_ts>2008-05-27 06:18:58</creation_ts>
<reporter>kxxxxxx@us.ibm.com</reporter>
<short_desc>We Couldn't Login in CMDB-DM while Creating usergroups withAd..</short_desc>
<delta_ts>2008-10-01 14:56:14</delta_ts>
<component>cmdb.ecmdb</component>
<prefix>p</prefix>
<bug_status>NEW</bug_status>
<bug_resolution></bug_resolution>
<bug_severity>High</bug_severity>
<assigned_to>jxxxxxxx@us.ibm.com</assigned_to>
....
</bug></bugzilla>

Import doesn't pick up the value 'p' in the file.

Am I reading all the docs wrong ? Is the bugzilla importer fixed in what
fields it's willing to import ?



--
Kevin Ramer ramerk@us.ibm.com
Tivoli Advisory Software Engineer

permanent link
Kevin Ramer (4.5k8183200) | answered Oct 17 '08, 12:18 p.m.
Ok,

THIS hurdle is solved by v 1.0.1 of RTC client. However now I need to discover if
I can direct the import to a specific workItemType ....

Thanks for your help.

Hi Kevin,

If I understand you correctly, you have created a custom attribute in the process spec and have modified the generated data mapping file to map the Bugzilla prefix field to this custom attribute. Your custom attribute should look something like this in the process spec:

<customAttributes>
<customAttribute>
</customAttributes>

Then in the generated mapping file, there should be an entry like this:
<attribute>
</attribute>

Lorelei
Jazz CQ Connector Team

Hello,

I've been battling Bugzilla imports and I'm trying to take a generated
mapping file and add 1 additional attribute. That looks like
this in the RTC repository (configuration xml)



<customAttributes>
<customAttribute>
</customAttributes>

I added this to a generated mapping xml:

<attribute>

And my bug source files look like:

<xml>
<bugzilla>
<bug>
<bug_id>24518</bug_id>
<creation_ts>2008-05-27 06:18:58</creation_ts>
<reporter>kxxxxxx@us.ibm.com</reporter>
<short_desc>We Couldn't Login in CMDB-DM while Creating usergroups withAd..</short_desc>
<delta_ts>2008-10-01 14:56:14</delta_ts>
<component>cmdb.ecmdb</component>
<prefix>p</prefix>
<bug_status>NEW</bug_status>
<bug_resolution></bug_resolution>
<bug_severity>High</bug_severity>
<assigned_to>jxxxxxxx@us.ibm.com</assigned_to>
....
</bug></bugzilla>

Import doesn't pick up the value 'p' in the file.

Am I reading all the docs wrong ? Is the bugzilla importer fixed in what
fields it's willing to import ?



--
Kevin Ramer ramerk@us.ibm.com
Tivoli Advisory Software Engineer

permanent link
Lorelei Ngooi (1.5k22) | answered Oct 17 '08, 12:30 p.m.
JAZZ DEVELOPER
Hi,

If the value of the Bugzilla field that you are mapping to the work item type matches the work item type ids (defect, enhancement, etc), then you can add an entry similar to the following in your data mapping:

<attribute>

Otherwise, you will need to add value mappings for the transformation.

Lorelei

Ok,

THIS hurdle is solved by v 1.0.1 of RTC client. However now I need to discover if
I can direct the import to a specific workItemType ....

Thanks for your help.

Hi Kevin,

If I understand you correctly, you have created a custom attribute in the process spec and have modified the generated data mapping file to map the Bugzilla prefix field to this custom attribute. Your custom attribute should look something like this in the process spec:

<customAttributes>
<customAttribute>
</customAttributes>

Then in the generated mapping file, there should be an entry like this:
<attribute>
</attribute>

Lorelei
Jazz CQ Connector Team

Hello,

I've been battling Bugzilla imports and I'm trying to take a generated
mapping file and add 1 additional attribute. That looks like
this in the RTC repository (configuration xml)



<customAttributes>
<customAttribute>
</customAttributes>

I added this to a generated mapping xml:

<attribute>

And my bug source files look like:

<xml>
<bugzilla>
<bug>
<bug_id>24518</bug_id>
<creation_ts>2008-05-27 06:18:58</creation_ts>
<reporter>kxxxxxx@us.ibm.com</reporter>
<short_desc>We Couldn't Login in CMDB-DM while Creating usergroups withAd..</short_desc>
<delta_ts>2008-10-01 14:56:14</delta_ts>
<component>cmdb.ecmdb</component>
<prefix>p</prefix>
<bug_status>NEW</bug_status>
<bug_resolution></bug_resolution>
<bug_severity>High</bug_severity>
<assigned_to>jxxxxxxx@us.ibm.com</assigned_to>
....
</bug></bugzilla>

Import doesn't pick up the value 'p' in the file.

Am I reading all the docs wrong ? Is the bugzilla importer fixed in what
fields it's willing to import ?



--
Kevin Ramer ramerk@us.ibm.com
Tivoli Advisory Software Engineer

permanent link
Lorelei Ngooi (1.5k22) | answered Oct 17 '08, 12:32 p.m.
JAZZ DEVELOPER
Sorry, I see the html was stripped.

<attribute sourceId="type" targetId="com.ibm.team.workitem.attribute.workitemtype" />

Lorelei

permanent link
Kevin Ramer (4.5k8183200) | answered Oct 17 '08, 4:20 p.m.
Sorry, I see the html was stripped.

<attribute sourceId="type" targetId="com.ibm.team.workitem.attribute.workitemtype" />

Lorelei



Ok, I don't quite follow where this would fit in. Are you saying that if I have that in my
mapping, I can say

<type>some-type</type>

somewhere at the beginning of my input xml ?

permanent link
Lorelei Ngooi (1.5k22) | answered Oct 17 '08, 4:42 p.m.
JAZZ DEVELOPER
Hi Kevin,

Short answer is yes.

Long answer is the data mapping file needs to contain the mapping between the Bugzilla fields and Jazz fields. If you want to map to the Jazz work item type field, the target id value would be "com.ibm.team.workitem.attribute.workitemtype". As an example, if you had a Bugzilla field named type that you wanted to map to the Jazz work item type, then you need to have

<attribute sourceId="type" targetId="com.ibm.team.workitem.attribute.workitemtype" />

in the data mapping file. Then in the data input file, there would be an xml tag for type:
<type>enhancement</type>

This is assuming that the value for type is an identical match of the work item type ids.

Lorelei

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.