Import Duplicated pair of bugs from Bugzilla to Jazz
We are working on migration from CQALM to Jazz via Bugazilla and found an interesting but annoying case.
The duplicated pair of bugs are imported to Jazz without error or warning. But if you modify an Closed item marked as Duplicate, like adding a Tag, then saving the item will automatically do the following too:
Status Closed → Reopened
Resolution Duplicate → Unresolved
Tags added: test
Resolved By STEFAN EBERL → Unassigned
I tested on the work itemes created in the Jazz directly and it does allow me to save the Closed item of Duplicate as it is when I tried to add to Tag field.
Comparing the two cases, I found that the imported work item lost their Duplicate link in the Link area. So is the question, how do I take care of the Links like duplication, dependon, etc when migrating from Bugzilla XML file to Jazz via Jazz importer? I know the <cc></cc> entry can make subscriber link mapped and imported correctly, do we have something similar for Duplicate, DependOn?
Any help is appreciated.
The duplicated pair of bugs are imported to Jazz without error or warning. But if you modify an Closed item marked as Duplicate, like adding a Tag, then saving the item will automatically do the following too:
Status Closed → Reopened
Resolution Duplicate → Unresolved
Tags added: test
Resolved By STEFAN EBERL → Unassigned
I tested on the work itemes created in the Jazz directly and it does allow me to save the Closed item of Duplicate as it is when I tried to add to Tag field.
Comparing the two cases, I found that the imported work item lost their Duplicate link in the Link area. So is the question, how do I take care of the Links like duplication, dependon, etc when migrating from Bugzilla XML file to Jazz via Jazz importer? I know the <cc></cc> entry can make subscriber link mapped and imported correctly, do we have something similar for Duplicate, DependOn?
Any help is appreciated.
13 answers
The example I gave just gives the particular bug's duplicates. If this bug is a duplicate of some other bug, then the comment format is the following:
<long_desc>
<who>kim_horne@ca.ibm.com</who>
<bug_when>2005-01-30 09:13</bug_when>
<thetext>*** This bug has been marked as a duplicate of 123. ***</thetext>
</long_desc>
For a particular bug,
1. To import its duplicates, include a long_desc tag with the format I gave previously. There can be more than one long_desc for each duplicate.
2. To import the bug that it is a duplicate of, then the resolution value should be DUPLICATE and construct the above long_desc.
Thanks, Lorelei,
I'll give it a shot.
The example I gave just gives the particular bug's duplicates. If this bug is a duplicate of some other bug, then the comment format is the following:
<long_desc>
<who>kim_horne@ca.ibm.com</who>
<bug_when>2005-01-30 09:13</bug_when>
<thetext>*** This bug has been marked as a duplicate of 123. ***</thetext>
</long_desc>
For a particular bug,
1. To import its duplicates, include a long_desc tag with the format I gave previously. There can be more than one long_desc for each duplicate.
2. To import the bug that it is a duplicate of, then the resolution value should be DUPLICATE and construct the above long_desc.
Thanks, Lorelei,
It works well except that the link created after import is called Mention, not Duplicate Of. Do I miss osmething or thta is the implementation?
page 2of 1 pagesof 2 pages