Bugzilla Import / Changing Link Types
Hi,
I want to import work items using the Bugzilla XML import wizard. Problem is that my work items represent stories and tasks and had a parent / child relationship in the original issue tracking system (ScrumWorks), whereas the Bugzilla XML format only seems to know <dependson> / <blocked> links.
So what I wanted to know is if there is, in the order of preference:
1.) a way to customize the import process so that the <dependson> / <blocked> links are interpreted as being parent / child
2.) a way to modify the link types after the import has completed, either in a batch-like mode or even on an individual basis - right now it seems to me that the only option I have is to remove and recreate each and every link.
I want to import work items using the Bugzilla XML import wizard. Problem is that my work items represent stories and tasks and had a parent / child relationship in the original issue tracking system (ScrumWorks), whereas the Bugzilla XML format only seems to know <dependson> / <blocked> links.
So what I wanted to know is if there is, in the order of preference:
1.) a way to customize the import process so that the <dependson> / <blocked> links are interpreted as being parent / child
2.) a way to modify the link types after the import has completed, either in a batch-like mode or even on an individual basis - right now it seems to me that the only option I have is to remove and recreate each and every link.
10 answers
I have the same general requirement. I would like to migrate from another tool for scalability reasons. In the current tool there already exists a structure as follows:
--Project
----Iteration
------User Story
--------Task
--------Task
------User Story
--------Task
--------Task
The current tool also has an XML export that follows the above structure.
It would be really nice to have a XML import mechanism that preserves the links and structure.
Another really nice to have would be a general XML Export/Import function that preserves the structure and links. This would be be very useful when moving projects to other repositories.
Moving our project to Team Concert without this function would be a daunting task.
--Project
----Iteration
------User Story
--------Task
--------Task
------User Story
--------Task
--------Task
The current tool also has an XML export that follows the above structure.
It would be really nice to have a XML import mechanism that preserves the links and structure.
Another really nice to have would be a general XML Export/Import function that preserves the structure and links. This would be be very useful when moving projects to other repositories.
Moving our project to Team Concert without this function would be a daunting task.
tingey wrote:
This could be useful:
https://jazz.net/learn/LearnItem.jsp?href=content/tech-notes/rational-team-concert-1_0-importing-work-items/index.html
The bugzilla importer supports custom mapping, so you can as well import
any XML as work items to the system as long as the mapping is correct.
--
Benjamin Pasero
Work Item & UI Commons Team
I have the same general requirement. I would like to migrate from
another tool for scalability reasons. In the current tool there
already exists a structure as follows:
--Project
----Iteration
------User Story
--------Task
--------Task
------User Story
--------Task
--------Task
The current tool also has an XML export that follows the above
structure.
It would be really nice to have a XML import mechanism that preserves
the links and structure.
Another really nice to have would be a general XML Export/Import
function that preserves the structure and links. This would be be
very useful when moving projects to other repositories.
Moving our project to Team Concert without this function would be a
daunting task.
This could be useful:
https://jazz.net/learn/LearnItem.jsp?href=content/tech-notes/rational-team-concert-1_0-importing-work-items/index.html
The bugzilla importer supports custom mapping, so you can as well import
any XML as work items to the system as long as the mapping is correct.
--
Benjamin Pasero
Work Item & UI Commons Team
Michael,
don't know if that's an option for you, but: I have decided to use the Jazz Plain Java Client libraries (https://jazz.net/downloads/rational-team-concert/releases/1.0.1.1?p=allDownloads) directly instead of using the Bugzilla import wizard. Took me some time to get used to it, but it just offers a lot more possibilities (including creating links of any type).
don't know if that's an option for you, but: I have decided to use the Jazz Plain Java Client libraries (https://jazz.net/downloads/rational-team-concert/releases/1.0.1.1?p=allDownloads) directly instead of using the Bugzilla import wizard. Took me some time to get used to it, but it just offers a lot more possibilities (including creating links of any type).
Suppport for the parent/child relationship has been added to the Bugzilla importer. Please see work item https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=67596. This was included in the 2.0 M2D1 release.
The mapping file has to be modified to include the parent/child relationship. Here's an example where the source fields Parent and Children are mapped to the work item parent/child relationships.
<attribute>
<attribute>
The mapping file has to be modified to include the parent/child relationship. Here's an example where the source fields Parent and Children are mapped to the work item parent/child relationships.
<attribute>
<attribute>
Suppport for the parent/child relationship has been added to the Bugzilla importer. Please see work item https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=67596. This was included in the 2.0 M2D1 release.
The mapping file has to be modified to include the parent/child relationship. Here's an example where the source fields Parent and Children are mapped to the work item parent/child relationships.
<attribute sourceId="Parent" targetId="com.ibm.team.workitem.rcp.core.parent"/>
<attribute sourceId="Children" targetId="com.ibm.team.workitem.rcp.core.children"/>
The mapping file has to be modified to include the parent/child relationship. Here's an example where the source fields Parent and Children are mapped to the work item parent/child relationships.
<attribute sourceId="Parent" targetId="com.ibm.team.workitem.rcp.core.parent"/>
<attribute sourceId="Children" targetId="com.ibm.team.workitem.rcp.core.children"/>
Christian,
Thanks for the info, I'll take a look at this. It might be a little deeper dive than I can do right now but still good to know.
Thanks,
Thanks for the info, I'll take a look at this. It might be a little deeper dive than I can do right now but still good to know.
Thanks,
Michael,
don't know if that's an option for you, but: I have decided to use the Jazz Plain Java Client libraries (https://jazz.net/downloads/rational-team-concert/releases/1.0.1.1?p=allDownloads) directly instead of using the Bugzilla import wizard. Took me some time to get used to it, but it just offers a lot more possibilities (including creating links of any type).
Lorelei,
Thank you for the update. Is 2.0 M2D1 a client statement? And if so is it compatible with a 1.0.1 server? Or do servers and clients have to stay in lock step?
quote="lngooi"]Suppport for the parent/child relationship has been added to the Bugzilla importer. Please see work item https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=67596. This was included in the 2.0 M2D1 release.
The mapping file has to be modified to include the parent/child relationship. Here's an example where the source fields Parent and Children are mapped to the work item parent/child relationships.
<attribute>
<attribute>
Thank you for the update. Is 2.0 M2D1 a client statement? And if so is it compatible with a 1.0.1 server? Or do servers and clients have to stay in lock step?
quote="lngooi"]Suppport for the parent/child relationship has been added to the Bugzilla importer. Please see work item https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=67596. This was included in the 2.0 M2D1 release.
The mapping file has to be modified to include the parent/child relationship. Here's an example where the source fields Parent and Children are mapped to the work item parent/child relationships.
<attribute>
<attribute>
Yes, the earliest client that has this fix is the 2.0 M2D1 client. And yes, the client and server have to be compatible so you would need to upgrade the server as well.
I should also add that the related work item relationship is also supported in the Bugzilla importer. Here is an example of what would need to be added to the mapping file to include that relationship:
<attribute sourceId="Related" targetId="com.ibm.team.workitem.rcp.core.related"/>
I should also add that the related work item relationship is also supported in the Bugzilla importer. Here is an example of what would need to be added to the mapping file to include that relationship:
<attribute sourceId="Related" targetId="com.ibm.team.workitem.rcp.core.related"/>
Lorelei,
Ok, good to know that client/server levels must match.
It's also good to know the Bugzilla importer supports the related work item relationship. Thanks for the example.
Ok, good to know that client/server levels must match.
It's also good to know the Bugzilla importer supports the related work item relationship. Thanks for the example.
Yes, the earliest client that has this fix is the 2.0 M2D1 client. And yes, the client and server have to be compatible so you would need to upgrade the server as well.
I should also add that the related work item relationship is also supported in the Bugzilla importer. Here is an example of what would need to be added to the mapping file to include that relationship:
<attribute>