Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

import from Jira via Bugzilla [Solved]

 we need to build tools to import a couple hundred Jira projects into RTC. (easy if its 1)..

we are trying to balance out the  work/support/... for three different ways

1. export to csv from jira, import into RTC..
      no attachments, links, comments
      have to write code to handle those
      like our rtc to rtc code now
2. all java
3. export to bugzilla, import from there. 
    http://bdunagan.com/2011/11/07/migrating-jira-to-bugzilla/
    handles attachments, links, comments, ....

using option 3 we have created bug files, then zipped them up (zip file contains, bug1.xml, bug2.xml, etc...)
then use the bugzilla importer with a custom mapping file. per https://jazz.net/library/article/69

but we get error 

bug BUG-1: Unexpected content, please check Bugzilla URL and authentication

there is no bugzilla server .. so?

| is there any doc on the format expected? maybe the script in point 3 has created the wrong bug format 

on edit
never mind,  scroll down in article 69 , gives format

1

1 vote

Comments

Hi, Sam. Do you still have a question? I can't quite tell from your edit if you cleared everything up yourself or just a piece of it. 

thanks for asking.. the specific question I asked I solved by looking further in the referenced doc, and we were able to convert one jira ticket to a form acceptable by the importer..

however.. the jira ticket was a Story, and we got a Defect in RTC.. wait BUG zilla..
is that all the importer will do? defects? 

I haven't rechecked the doc to see if there is a tag that specifies 'type' in the 'bug' xml..

so, if you've got a pointer or some cool knowledge, I'm open to being pointed in the direction I need to go.!


Accepted answer

Permanent link
 we have successfully imported a bug->defect 
but need to get more workitem types

so, using type as an additional tag, and adding type to the mapping file 'should work', but doesn't
<pre>
works, get defect
  <bug>
    <bug_id>STORM-1000</bug_id>
    <creation_ts>2014-02-06 16:50</creation_ts>
    <short_desc>[STORM-1000] Re-factor - WSDL (ML2) - Country</short_desc>
    <delta_ts>2014-02-06 17:20:29</delta_ts>
    <reporter_accessible>1</reporter_accessible>
    <cclist_accessible>1</cclist_accessible>
    <classification_id>1</classification_id>
    <classification>Unclassified</classification>
    <product></product>
    <version>unspecified</version>
    <rep_platform>All</rep_platform>
    <op_sys>All</op_sys>
    <bug_status>NEW</bug_status>
    <resolution></resolution>
    <reporter name=''></reporter>
    <assigned_to name=''></assigned_to>
    <status_whiteboard>N/A</status_whiteboard>
    <priority>P6</priority>
    <bug_severity>Sev2</bug_severity>
    <target_milestone>unspecified</target_milestone>
    <everconfirmed>1</everconfirmed>
  </bug>

doesn't work, get error
Could not create work item from bug STORM-1000
Could not create work item from bug BUG-0001: CRRTC0290E: The work item cannot be saved because the work item's type is not configured correctly at the project level. 

  <bug>
    <bug_id>STORM-1000</bug_id>
<type>Story</type>
    <creation_ts>2014-02-06 16:50</creation_ts>
    <short_desc>[STORM-1000] Re-factor - WSDL (ML2) - Country</short_desc>
    <delta_ts>2014-02-06 17:20:29</delta_ts>
    <reporter_accessible>1</reporter_accessible>
    <cclist_accessible>1</cclist_accessible>
    <classification_id>1</classification_id>
    <classification>Unclassified</classification>
    <product></product>
    <version>unspecified</version>
    <rep_platform>All</rep_platform>
    <op_sys>All</op_sys>
    <bug_status>NEW</bug_status>
    <resolution></resolution>
    <reporter name=''></reporter>
    <assigned_to name=''></assigned_to>
    <status_whiteboard>N/A</status_whiteboard>
    <priority>P6</priority>
    <bug_severity>Sev2</bug_severity>
    <target_milestone>unspecified</target_milestone>
    <everconfirmed>1</everconfirmed>
  </bug>
</pre>

mapping file 
<pre>
<attribute sourceId="type" targetId="com.ibm.team.workitem.attribute.workitemtype">
----> <value SourceId="Story" targetId="com.ibm.team.apt.workItemType.story" />
</attribute>
</pre>

<pre>
notice the tag element name is mixed case.. importer not happy!
<value sourceId="Story" targetId="com.ibm.team.apt.workItemType.story" />  works
</pre>

Ralph Schoon selected this answer as the correct answer

1 vote

Your answer

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 17
× 13

Question asked: Mar 27 '14, 2:46 p.m.

Question was seen: 6,947 times

Last updated: Mar 28 '14, 10:30 a.m.

Confirmation Cancel Confirm