How is the sequencing of Workitem ID managed?

Pravin Patil (104●1●32●130) | asked Sep 09 '15, 12:23 p.m.

I added 2 work items and the sequencing was off. 406 (SCR work item type) and 427 (SIR work item type). Is this expected behavior?

Should not the work item IDs have been in sequence like 406 and 407 if created one after another quickly?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

permanent link

sam detweiler (12.5k●6●194●201) | answered Sep 09 '15, 12:36 p.m.
edited Sep 09 '15, 12:36 p.m.

there is only one counter, so all requests for workitems, system wide, will increment the number.
and as I understand it when a workitem is starting to be created is when the counter is incremented, not when it is saved

Comments

Kevin Ramer commented Sep 09 '15, 3:45 p.m.

By "system wide" Sam means within a single RTC repository.

Pravin Patil commented Sep 09 '15, 6:45 p.m.

Is it possible that the ID gets generated randomly and not sequentially?

Because, I added 2 items and the sequencing was off. 406 (SCR work item type) and 427 (SIR work item type. I doubt there were 11 items created in the middle of the night...

Please let me know.

sam detweiler commented Sep 09 '15, 7:07 p.m.

always been sequential. but lots of things consume numbers.

Pravin Patil commented Sep 09 '15, 9:07 p.m.

"lot of things" like?

permanent link

Pravin Patil (104●1●32●130) | answered Sep 10 '15, 11:52 a.m.

I see 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 number....?

Comments

Kevin Ramer commented Sep 10 '15, 12:01 p.m.

There could be those work item numbers in project areas for which you have no access. It is also possible work items have been deleted.

It's all about the answers!

Related questions

How is the sequencing of Workitem ID managed?

2 answers

Your answer