CQ to RTC , Data Warehouse updation

If you are using the CQ Import wizard, then the work item's creation date will be set to the CQ record's submit date if the mapping file contains that mapping and if the query's display fields contain the submit date. Otherwise, the work item's creation date will be set to the current time.

If you are using the CQ Import wizard, then the work item's creation date will be set to the CQ record's submit date if the mapping file contains that mapping and if the query's display fields contain the submit date. Otherwise, the work item's creation date will be set to the current time.

How about the last modification date? What is it set to?

The last modification date is not directly set by the importer. It would be set as a result of creating the work item, so it would be set to the current time.

The CQ Importer is a new feature in 2.0 that is built on top of the Bugzilla importer. It executes an existing CQ query to determine which CQ records and record fields to import.

To use the Bugzilla importer in RTC 1.01, you must have created your own xml files that are consumable by the Bugzilla importer. If the xml files contain a creation_ts field, that would be used to set the work item's creation date field. Otherwise, the work item's creation date field would be set to the current time.

I believe my previous comment on the work item's last modification date holds, that is, it would be set to the current time.

On 7/30/2009 3:38 AM, littleheartb4u wrote:

Hi ,

We are trying to move from ClearQuest to RTC. We did a test migration
and the data looks good. As I understand, the snapshots in the
datawarehouse will be empty. Is there a way to update the snapshots
with the migrated data.

Thanks,
Bharath

1. Wait until midnight, they will run automatically.

2. Give a user the JazzAdmin and JazzDWAdmin privileges. As that user,
go to the reports web ui. Click on the "Administer Data Warehouse" link
and click the button to update all snapshots. You can monitor the
progress with the active services tab in the server admin web ui.

james
RTC Reports Team Lead

Hi James,

I did try those options already but it didn't help. From my understanding, only when we make a change to a migrated work item or create a new work item the snapshots will be built from that day. The previous CQ history will be lost. Is that so or am I missing something?

--Bharath

It could be that before you migrated you CQ data you already had some work items. Then somehow the import of the CQ data inserted items whose modification dates are prior to the already existing work items. If that is case, then the data warehouse collection task, will not see those work items.
One way to fix this is to:
1) import the CQ data into an empty repository that has no work items.
2) build the data warehouse.
3) export it to a file.
4) go back to your real repository.
5) empty the data warehouse.
6) import the file you exported in step 3.

Steps 3 and 6 are not documented in the RTC online help. So please raise a work item about this issue and we will give you better instructions.
The CQ team is also welcome to suggest a better solution to this.

Did you use the CQ Import wizard to import the CQ data into RTC?

I'm a co-worker's for the original poster (he was out - thanks for all the replies!). We're not using the CQ importer to import the data. This is a 1.0.1 instance and we are using the bugzilla importer because of the significant disparity between our schema in CQ and the schema in RTC.

In case anyone wonders why we haven't switched to 2.0 and the csv importer - we have some significant development effort already sunk in the bugzilla importer so do not want to switch mechanisms at this time.

Does the fact that we are using the bugzilla importer change any of the suggestions?

The CQ Importer is a new feature in 2.0 that is built on top of the Bugzilla importer. It executes an existing CQ query to determine which CQ records and record fields to import.

To use the Bugzilla importer in RTC 1.01, you must have created your own xml files that are consumable by the Bugzilla importer. If the xml files contain a creation_ts field, that would be used to set the work item's creation date field. Otherwise, the work item's creation date field would be set to the current time.

I believe my previous comment on the work item's last modification date holds, that is, it would be set to the current time.

Lorelei,
Yes. We are creating our own XML files and use creation_ts field to map the original CQ record's creation date over and thta works well.

We also use delta_ts to map the last modification date, which is hown in the history of the imported reocrd on RTC as Last change (Bugzilla)