Has anyone tried Bugzilla to Jazz work item migration?
25 answers
I don't think it's a bug with the Bugzilla importer. The xml file representing the Bugzilla bug is from Bugzilla not the Bugzilla importer. Also, the Bugzilla importer can handle a mapping file with an entry for the description field.
A workaround would be to modify the Bugzilla xml file by adding a separate description tag and moving the content of the text of the first long desc tag into this field. Then add a mapping for the description field.
Example mapping entry for the description field:
<attribute sourceId="description" targetId="com.ibm.team.workitem.attribute.description" />
A workaround would be to modify the Bugzilla xml file by adding a separate description tag and moving the content of the text of the first long desc tag into this field. Then add a mapping for the description field.
Example mapping entry for the description field:
<attribute sourceId="description" targetId="com.ibm.team.workitem.attribute.description" />
Example mapping entry for the description field:
<attribute>
I tried that but it doesn't work. I get a java error saying: "java.lang.NullPointerException". I tried to use another name for the sourceId, still the same.
Looks to me that bugzilla importer limits the abilites to the bugzilla specification, and does not allow any flexabiltity to overcome such problems.
DanielM wrote:
Can you open a bug report on this against 'Work Item' filling out all
details. Thanks.
--
Benjamin Pasero
Work Item & UI Commons Team
lngooiwrote:
Example mapping entry for the description field:
attribute
I tried that but it doesn't work. I get a java error saying:
"java.lang.NullPointerException". I tried to use another
name for the sourceId, still the same.
Can you open a bug report on this against 'Work Item' filling out all
details. Thanks.
--
Benjamin Pasero
Work Item & UI Commons Team
We are actually on 2.0. Do you have a simple example of a xml for this you could post here?
The question is in which tag is the description of the bug, when the comments are in long_desc?
You'll need to modify two XML files to get it work:
One is Bugzilla report in XML format and here you need to have an entry like:
<description>Description\<description>
The other file is the mapping file used by the importer and oyu need to have an entry like:
<attribute>
<attributeType>
<value>
</attributeType>
Guess I acted too fast.
I was told that the <description> attribute would work on 2.0 but apprently it is not.
I just tested on my 2.0 server and the importer can't pick up and fill the Description attribute. I still have to use the <desc_long> field to get it work but of course you end up with a duplicated Description entry in the Comments attribute too, just like in 1.0.1.1.
I was told that the <description> attribute would work on 2.0 but apprently it is not.
I just tested on my 2.0 server and the importer can't pick up and fill the Description attribute. I still have to use the <desc_long> field to get it work but of course you end up with a duplicated Description entry in the Comments attribute too, just like in 1.0.1.1.
I was going to submit a bug report for the duplicated Decription display issue supposed to be fixed on 2.0 RTC.
But as I prepare the mapping file, I found out that I commented off the entry for <description> attribute when used it to do the import.
So I gave it another try and it works this time. We finally get rid off the redundante display of the bug Description in both RTC Description and Comments attribute.
But as I prepare the mapping file, I found out that I commented off the entry for <description> attribute when used it to do the import.
So I gave it another try and it works this time. We finally get rid off the redundante display of the bug Description in both RTC Description and Comments attribute.
page 2of 1 pagesof 2 pagesof 3 pages