Importing Notes_Log from CSV (NOT from ClearQuest)
![](http://jazz.net/_images/myphoto/a340bf9bfd70851662d89f4a5d014ef8.jpg)
I am trying to import issues from another bug tracking system into our RTC instance. I am using the "Import Work Items from CSV" capability.
From reading other forum posts, it appears that you cannot put a mapping to the discussion field in the mapping XML file. When importing ClearQuest records, though, if there is a field called Notes_Log, the importer will supposedly correctly fill in the discussion field in RTC.
In my CSV we have a column that is analogous to the discussion field. So I renamed the column header as "Notes_Log" and was hoping that the comments would appear in the discussion field. However, nothing comes in. I suspect that maybe the text in that field needs to be in some specific format that the importer understands in order to correctly parse out the date and user? Can someone provide me what that format is supposed to be?
Thanks in advance,
Mike Johnson
From reading other forum posts, it appears that you cannot put a mapping to the discussion field in the mapping XML file. When importing ClearQuest records, though, if there is a field called Notes_Log, the importer will supposedly correctly fill in the discussion field in RTC.
In my CSV we have a column that is analogous to the discussion field. So I renamed the column header as "Notes_Log" and was hoping that the comments would appear in the discussion field. However, nothing comes in. I suspect that maybe the text in that field needs to be in some specific format that the importer understands in order to correctly parse out the date and user? Can someone provide me what that format is supposed to be?
Thanks in advance,
Mike Johnson
6 answers
![](http://jazz.net/_images/myphoto/a340bf9bfd70851662d89f4a5d014ef8.jpg)
I am trying to import issues from another bug tracking system into our RTC instance. I am using the "Import Work Items from CSV" capability.
From reading other forum posts, it appears that you cannot put a mapping to the discussion field in the mapping XML file. When importing ClearQuest records, though, if there is a field called Notes_Log, the importer will supposedly correctly fill in the discussion field in RTC.
In my CSV we have a column that is analogous to the discussion field. So I renamed the column header as "Notes_Log" and was hoping that the comments would appear in the discussion field. However, nothing comes in. I suspect that maybe the text in that field needs to be in some specific format that the importer understands in order to correctly parse out the date and user? Can someone provide me what that format is supposed to be?
Thanks in advance,
Mike Johnson
Hi Mike
I don't know the exact format - but I did try exporting a set of work items with comments - and looked at the resultant output.
The comments are in the format
Name Date
Comment
A silly test output looks like this:
Anthony Kesterton - 25/02/2011 17:13
Comment A
Anthony Kesterton - 25/02/2011 17:13
Add another comment
Anthony Kesterton - 25/02/2011 17:13
Stuff
This was all in the same CSV cell.
I wonder if that works on the import too - worth a try...
anthony
![](http://jazz.net/_images/myphoto/a340bf9bfd70851662d89f4a5d014ef8.jpg)
I'm not sure about importing comments using the csv format, but if you use an xml format, you can import them. Look at the Importing from Other Issue Tracking Systems section in http://jazz.net/library/LearnItem.jsp?href=content/tech-notes/rational-team-concert-1_0-importing-work-items/index.html to see the format to handle comments via the long_desc field.
![](http://jazz.net/_images/myphoto/a340bf9bfd70851662d89f4a5d014ef8.jpg)
Comments are supported from CSV. The name of the column for comments has
to match with the comments
field in the target project area. Try export a work item from RTC via
CSV and select comments then you see
the name. I think its "Discussion" instead of comments.
Ben
On 25.02.2011 6:53, lngooi wrote:
to match with the comments
field in the target project area. Try export a work item from RTC via
CSV and select comments then you see
the name. I think its "Discussion" instead of comments.
Ben
On 25.02.2011 6:53, lngooi wrote:
I'm not sure about importing comments using the csv format, but if
you use an xml format, you can import them. Look at the Importing
from Other Issue Tracking Systems section in
http://jazz.net/library/LearnItem.jsp?href=content/tech-notes/rational-team-concert-1_0-importing-work-items/index.html
to see the format to handle comments via the long_desc field.
![](http://jazz.net/_images/myphoto/a340bf9bfd70851662d89f4a5d014ef8.jpg)
Ben,
Tried that as well. It gets exported as "Comments." I get no results if I name the field Comments or if I name it Discussion.
I wanted to take a look @ the Eclipse client source code and see if I can discern what's going on, but it appears that the RTC client source code isn't on jazz.net anymore. I swear I remember that source code being on jazz.net for RTC 2.0 and below?? Am I crazy or what?
Thanks,
Mike
Tried that as well. It gets exported as "Comments." I get no results if I name the field Comments or if I name it Discussion.
I wanted to take a look @ the Eclipse client source code and see if I can discern what's going on, but it appears that the RTC client source code isn't on jazz.net anymore. I swear I remember that source code being on jazz.net for RTC 2.0 and below?? Am I crazy or what?
Thanks,
Mike
![](http://jazz.net/_images/myphoto/a340bf9bfd70851662d89f4a5d014ef8.jpg)
We should follow up in a bug report on RTC against Work Items component,
please cc me.
On 28.02.2011 10:22, micjohnson997 wrote:
please cc me.
On 28.02.2011 10:22, micjohnson997 wrote:
Ben,
Tried that as well. It gets exported as "Comments." I get
no results if I name the field Comments or if I name it Discussion.
I wanted to take a look @ the Eclipse client source code and see if I
can discern what's going on, but it appears that the RTC client
source code isn't on jazz.net anymore. I swear I remember that
source code being on jazz.net for RTC 2.0 and below?? Am I crazy or
what?
Thanks,
Mike