Has anyone tried Bugzilla to Jazz work item migration?
Please can you share your experience and post sample XML files you used to do the export from Bugzilla, import to Jazz and the mapping gfile if you use?
|
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" /> |
Example mapping entry for the description field: 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:
lngooiwrote: 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? 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> |
Need to use the code tag:
|
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. |
If that is true, then it is a bug. Please submit a work item on that.
|
If that is true, then it is a bug. Please submit a work item on that. Lorelei, Will do after I run another around of import test tomorrow. |
ghu wrote:
lngooiwrote: Thanks, please add me as subscriber. -- Benjamin Pasero Work Item & UI Commons Team |
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. |
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.