Work Item Import - is there a log file?

I'm running into a similar issue. I did find mention of turning on the Error Log in http://jazz.net/library/article/391:

Make sure that you are displaying the error log so that you can see the invalid ID errors. To display the error log in the RTC CQ Importer, select Window > Show View > Other > General > Error Log.

The error log displays an error in the following form to indicate that the CQ records contain an ID (e-mail address) that is not a valid user in the RTC server.

The user "fred@example.com" is not authorized to perform the operation. The "JazzAdmins" role is required to perform this operation.

The only error I see is when the import tries to save the work item. My problem is occurring with the data not being mapped/imported as I expect, but there's nothing telling me what's going on during the import, so I'm left to guess by hacking up the custom data mapping XML file.

The field I'm having trouble with is "Filed Against", which ties to the work item categories. I'm trying to map CQ components to multi-level work item categories in a manner other than the default Product/Component. I'm not sure where I'm messing up the mapping. Since this field is required, the save always fails.

Would be nice to be able to enable debugging, perhaps with a flag in the mapping.xml file, that spits out which CQ values are being mapped to which RTC values prior to the saving of the record being attempted.

Hi,

I haven't done this for a while but I was typically most successful when starting small. I tried to import only one or two items into a test project. This allows to play with the mapping in a controlled fashion.

One thing you could try on a test server too, is to make "filed against" not required. This would help to get at least that issue resolved and possibly get some data to look at and expand on. Then you could play with the "filed against" mapping.

I am not sure there is more logging available, I'd check in the Eclipse workspaces .metadata directory. You could create a work item to ask for more logging too.

Ralph

I'm running into a similar issue. I did find mention of turning on the Error Log in http://jazz.net/library/article/391:

Make sure that you are displaying the error log so that you can see the invalid ID errors. To display the error log in the RTC CQ Importer, select Window > Show View > Other > General > Error Log.

The error log displays an error in the following form to indicate that the CQ records contain an ID (e-mail address) that is not a valid user in the RTC server.

The user "fred@example.com" is not authorized to perform the operation. The "JazzAdmins" role is required to perform this operation.

The only error I see is when the import tries to save the work item. My problem is occurring with the data not being mapped/imported as I expect, but there's nothing telling me what's going on during the import, so I'm left to guess by hacking up the custom data mapping XML file.

The field I'm having trouble with is "Filed Against", which ties to the work item categories. I'm trying to map CQ components to multi-level work item categories in a manner other than the default Product/Component. I'm not sure where I'm messing up the mapping. Since this field is required, the save always fails.

Would be nice to be able to enable debugging, perhaps with a flag in the mapping.xml file, that spits out which CQ values are being mapped to which RTC values prior to the saving of the record being attempted.

Thanks Ralph. I'm working with Gerry on this and we are just trying to import one defect record. The category mapping we are doing is the simple form as shown in in this https://jazz.net/wiki/bin/view/Main/CQImportWizardTips wiki article like this...
<attribute>

We have the Category setup which mappings EXACTLY to the CQ Product/Component concatenation. Looks like this
DATASTAGE TX/ADAPTER ORACLE AQ

We could really use some help from the CQ Importer Folks at this point.

Thanks Ralph. I'm working with Gerry on this and we are just trying to import one defect record. The category mapping we are doing is the simple form as shown in in this https://jazz.net/wiki/bin/view/Main/CQImportWizardTips wiki article like this...
<attribute>

We have the Category setup which mappings EXACTLY to the CQ Product/Component concatenation. Looks like this
DATASTAGE TX/ADAPTER ORACLE AQ

We could really use some help from the CQ Importer Folks at this point.

Looks like the xml mapping example didn't post correctly, but in the wki document thye have an example on simple mapping a CQ Product/Component to the category attribute and that's what we have done.

Hi Thomas,

just one question, did you create the category you want to map to in RTC? I am not sure the import will create those automatically.

Just a thought.

Ralph

Thanks Ralph. I'm working with Gerry on this and we are just trying to import one defect record. The category mapping we are doing is the simple form as shown in in this https://jazz.net/wiki/bin/view/Main/CQImportWizardTips wiki article like this...
<attribute>

We have the Category setup which mappings EXACTLY to the CQ Product/Component concatenation. Looks like this
DATASTAGE TX/ADAPTER ORACLE AQ

We could really use some help from the CQ Importer Folks at this point.

I took a look at your mapping file and you have two mappings to the work item category field (aka filed against). The first one has the concatenated fields which sounds like what you want.

<attribute sourceId="Product/Component" targetId="com.ibm.team.workitem.attribute.category"/>

The second one is probably from our sample mapping file.

<attribute sourceId="Project" targetId="com.ibm.team.workitem.attribute.category"/>

So, you want to keep the first mapping and remove the second. Your data file probably doesn't have a Project field and sending over an empty value for category.

I took a look at your mapping file and you have two mappings to the work item category field (aka filed against). The first one has the concatenated fields which sounds like what you want.

<attribute>

The second one is probably from our sample mapping file.

<attribute>

So, you want to keep the first mapping and remove the second. Your data file probably doesn't have a Project field and sending over an empty value for category.

Yes. We found that about 40 minutes ago. Our Bad.