RTC - how to reset record id for a project area?

So If I really want to use my original ticket numbers starting at 1 I would need to have a new RTC repository created just for my project?

correct, and sometimes the numbers are not contiguous..    there are cases where canceling creating a workitem will still consume an id value.

generally in migrations like this we suggest adding another field to show the original ID so that its searchable (/old_number  in the search box will find old_number in a field) 
old number is just for migration.. new workitems wouldn't have this.. so for a short time u deal with both, then just the normal workitem ID

I have thought about using a custom field to store the ticket number from the old system but we do have a number of other documents referring to the old ticket number which I think can easily lead to confusion, at least when viewing historical items. Some of these tickets do have long lifetimes (e.g. several years) as well.

Previously, I found "TN0007: Guide for importing Jazz work items from Bugzilla and other systems (https://jazz.net/library/article/69) although it is somewhat dated now. It didn't address this migration issue.

I'm going to talk to our RTC repo admin to see about setting up another repo just for our project. Thanks for the information.

Nice tip. Is there an example of setting this up somewhere? Can you override the system wide work item id with the custom ID when displaying work items in query results? That is, do we have edit control over the layout of the query results? If I could hide the system wide id and just show the custom ID in certain query results, this might make it more palatable.

You can control the editor display and the query-results display to show your ID in a very visible place, but the system-defined ID is hardwired into a few critical places like the "search" box and in the work item URLs.   So the more prominent you make your ID, the more likely your users are to make the mistake of using your ID in those places where the system-defined ID is expected.

No. the number used for the ID is not controllable.  starts at 1 and counts up

Thanks Ralph for your valuable input.

Ralph,
I have created workitems with cutsom Ids in RTC i.e 9999* . Able to successfully create the workitem with custom id via CSV import. Now the problem is automatic Id counter has started increasing from 9999* instead of previous value.


Any work around or suggestion to sort out this.
if creation of new workitems in terms of data would be safe ?

I am mot the creator of the extension. As I think it comes with code, I would suggest you understand the code and make it work for you.

If you import CSV and provide the ID and activate updating the items, then the items found by ID are updated. Otherwise leve the ID column out and a new ID is created starting with the last available ID in the repository.

To be honest, I don't understand what you are doing, trying to do and what environment you use. If you provide the ID in an import without update mode with CSV, the importer will try to use the ID given (I think as I have done that years ago). If that is already taken it will take an ID that is not, You can't be sure that the work item will actually have the ID.  You can update If you provide the ID

To be quite clear here: you don't have any control about the ID that RTC uses for work items beyond what I explained above. You can use a custom attribute as a custom ID, if you want to do some magic and control that value. As explained in this community contributed extension for creating a custom consecutive ID: Extension to generate unique custom work item numbers you can create automation for that as well.

If that does not answer your question, I suggest you open a new question, instead of posting to one that is already answered.