.CSV File imports into RTC is causing the system ID to jump to several thousand IDs ahead..Any ideas as to why this happens?
Using the import utility in RTC, I am importing a .CSV file that is mapped to the corresponding fields in CLM. This import consists of CCRs (workitems) in the file with fields we want to export over from ClearQuest. It seems like the system automatically generates an Id number so high that it is throwing everything off. For example, the CCR import would have the headline, description, priority, etc. on the file....and once imported the system does not use the sequential numbering it has established i.e 1115..................it jumps to 7000 or something. I can't seem to figure out why it is doing this. So, when we are back to creating new CCRs....it takes the new series of numbers and goes sequentially from there! Feeling stumped over here...any guidance would be greatly appreciated.
One answer
Comments
thank you for the response. I am sending over data without the Id field and the system automatically generates the number? all the way up? Is there a way to change IDs in RTC without disrupting anything?
Work item ID numbers within RTC are unique and are generated by an internal number generator. They are usually sequential and new ones are assigned starting at {current newest work item ID in the repository}+1. The process of assigning a work item ID number is automatic and there's no way to change it that I'm aware of.
If you import and include the ID and tell the system to upgrade, I think you can force an ID. I think I have done that in the past. I can't be sure though.
Just tried importing with "Update" from .CSV into RTC 6.0.1. The import ignored the ID I provided in the .CSV and instead added a work item with the incremented unique ID.