<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/nwe.png" alt="new.png" width="50" height="50" align="right">Why is my !ClearQuest Import failing with error !CRRTC0290E? %DKGRAY% Authors: Main. IntegrationsTroubleshootingTeam<br> Build basis: IBM Rational Team Concert 4.x, Rational ClearQuest 4.x or later %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> ---++ Initial Assessment ---+++ Symptoms You are about to import !ClearQuest records with the !ClearQuest import Wizard from an archive into a Project Area based on a custom process template. The records are not imported but the following error appears: "Could not create work item from bug <ClearQuest ID>: !CRRTC0290E: The work item cannot be saved because the work item's type is not configured correctly at the project level". ---+++ Impact / Scope This issue is affecting all !ClearQuest Imports that are not mapped correctly to a corresponding work item type in the target project area when using the !ClearQuest Import Wizard ---++ Data gathering and subsequent analysis steps * The exported process from the Project Area * The zipped file that contains the !ClearQuest records * The mapping file used for the import ---++ Possible Solutions * Make sure that the record type of the exported !ClearQuest record is part of the xml</br> The tag is called <record_type></br> Every xml file with a !ClearQuest record has the following tag</br> <record_type><clearquest record type></record_type></br> <clearquest record type> has to be replaced with a record type like Defect * Make sure that the record type from the xml file is mapped to a corresponding Workitem type in the process used for the Project Area. * Make sure that the id is correct.</br></br> The mapping rule looks like:</br> targetId="com.ibm.team.workitem.attribute.workitemtype"> </br> <value sourceId="<clearquest record type>"targetId="<id for the Workitem of type defect>"/> </br> <clearquest record type> has to be replaced with a record type like Defect.</br> <id for the Workitem of type defect> has to be replaced with the correct id from the process the target Project Area is based on.</br></br> To find the id: 1. Open the target Project Area in RTC Eclipse client 1. On the tab Process Configuration expand Project Configuration - Configuration Data - Work Items - Types and Attributes 1. Select the target work item type and check the ID.</br><img alt="workitem_id.jpg" src="%ATTACHURL%/workitem_id.jpg" /> Still need help troubleshooting your integrations issue? Refer to <a href="IntegrationsTroubleshootingTeam" target="_blank">ClearQuest Import Wizard Limitations and known Problems </a> ---+++++!! Related topics: [[DeploymentWebHome][Deployment web home]] ---+++++!! External links: * !ClearQuest Knowledge Center Topic: <a href="Migrating Rational !ClearQuest records to work items" target="_blank">Migrating Rational !ClearQuest records to Work Items</a> * [[https://www.ibm.com][IBM]] ---+++++!! Additional contributors: Main.ElisabethCarbone ---+++++!! Questions and comments: %COMMENT{type="below" target="WhyIsMyClearQuestImportFailingWithErrorCRRTC0290EComments" button="Submit"}% %INCLUDE{"WhyIsMyClearQuestImportFailingWithErrorCRRTC0290EComments"}% <sticky></div></sticky>
This topic: Deployment
>
WebHome
>
DeploymentTroubleshooting
>
IntegrationsTroubleshooting
>
IntegrationsTroubleshootingJazzandClearQuest
>
WhyIsMyClearQuestImportFailingWithErrorCRRTC0290E
History: r2 - 2014-06-10 - 19:52:20 - Main.dmmckinn
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
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
.