How to find out missing numbers from workitem ID sequence?
I added 2 work items and the sequencing was off. 406 (SCR work item type) and 427 (SIR work item type).
I learned that, there is only one counter, so all requests for workitems, within a project area, will increment the numbers.
But I see that there are no other workitems created between 406 and 427, how to figure out what happened with the sequencing and what took away the missing numbers from sequence?
4 answers
the only thing you CAN say is that the number ill INCREASE between two workitems created in sequence.
the internal details of when the counter gets increments are not documented.
Comments
It was late night and I don't think any body must have created so many workitems in one night and deleted them. Am I missing something that I need to be aware of from workitems ID generation?
I tried searching for workitems 407, 420, and get the below error:
Why is this such a burning issue ? There is a single counter for work item id used by all project areas within an RTC repository. Unless you are a JazzAdmin you could get the error because you cannot read some work item or another because it is not in a project area for which you have read authority. I'd suggest taking this up with the administrators of your rtc repository.
Thanks for your response. I understand this is not a burning issue but it will be to the project when I start migrating workitems from my current system into RTC and the workitem ID's go off sequence with I having no proper explanation on why it happened...
I am the JazzAdmin for the project area but was still getting the error (that I provided above) while trying to access workitems between 406-427.
What are your thoughts, why would the ID's disappear?
If you import from another system, you can add a custom attribute of type text where you can store the original number for reference in older documents. You will never be able to import the work items with the same numbers of your old system.
yes, got that.
I am referring to, if I import 999 workitems, there ID that get generated are expected to be sequential...but from above scenario it doesn't look confirmed.
Also, if my last workitem in RTC is 101, will the next one that I import be 102 for sure?
If nothing else is happening on this server, it should be sequential, but there is no guaranty. when I worked on a migration process at one prior customer, we imported 15,000 workitems on a system where my job was the only one doing this work.
I did not check if the workitem ids were sequential, but from memory I don't remember any particular gaps.
Comments
I hear what you say. Also, there is no GREAT business reason or enforcement to have the IDs in sequence.
However, I am just trying to understand on what happened that some of the IDs went missing when they are supposed to be sequential and unique, good to know, isn't it?
you can choose not to reply to this comment, since it may not be as important to all...
The question was already answered. RTC uses a unique key (integer) and assigns that key as ID to each work item that is created in the repo. Usually all used IDs will be present in the repository, but they might be spread across multiple project areas.
ID's can become unused if the work item is deleted. I don't think these ID's will be reused.
1 vote
I think I didn't explain my situation correctly....
I created a work item and got its ID as 406. Then immediately I created another work item and got ID as 427. Its impossible that users must have created and deleted 427-406=21 work items in such short time gap.
I accept that RTC creates unique sequential ID's for work items, but in my case it was not sequential and hence I was trying to figure out on what happened with the ID's between 406 to 427.
This is not impacting my work anyways, but just good to know.
The ID is assigned if you save the work item, not if you "Create" it in the UI. Whatever, I'll unsubscribe now, as this costs far more precious time than it should.