| || |
Requirement Types in QC 9.2
We are upgrading from QC 9.0 to 9.2, and are having trouble when we publish our requirements from CaliberRM into QC 9.2. When publishing, the requirements are mapped to the RQ_REQ_Type field, which is now obsolete in 9.2, and the requirements are being loaded as Undefined requirement type. In Site Admin we have configured the requirement types to the values we are using in CaliberRM.
My questions is, what do we need to change to prevent our requirements from being loaded as Unidentified requirement type? Can someone explain the Unidentified requirement type? We somehow need to configure to identify the Business Requirements and Functional Requirements that are being published from Caliber with the appropriate numeric value associated with the new requirement type field in 9.2
Any help would be greatly appreciated :-)
Re: Requirement Types in QC 9.2
As long as you are using the built-in support within CaliberRM to publish your requirements, you do not have an obvious option. CaliberRM was designed to support Quality Center 9.0, not the Requirement enhancements in 9.2. Since Requirement Types are new for 9.2, CaliberRM doesn't know how to handle them. Borland is currently working to upgrade support for Quality Center 10, so I expect this will be resolved with their release.
In the meantime, you'll have to write something yourself to fix the requirement types. You can either use the OTA API to manipulate requirements, or you could run updates on the database.
Unfortunately, there's no good way to ensure that your "fix" gets executed after someone does a publish operation.