Why are numbers in the serie skipped

[palmen]

When creating a new Story in the SDLC module, it get number STRY0000001.

Scenario 1

If I click on save and then "Create New" (under Stories in SDLC) the next story will get STRY0000002 as the number.

Scenario 2

If I click on submit instead and then "Create New" then next story will get STRY0000003 as the number (skipping STRY000002)

Scenario 3

If I click on submit and afterwards on the "New" button on top of the Stories list, the next story will have number STRY0000004 (skipping STRY0000002 and STRY0000003)

How come some numbers in the serie are skipped depending on if I use save/submit and Create New/New?

In scenario 1, I'll get the next number in the serie.

In scenario 2, it'll skip 1 number

In scenario 3, it'll skip 2 numbers

[Chuck Tomasi]

Hi Fredrik,

Thank you for the details. Very informative. I would check for business rules on this table that could be doing erroneous calls to insert(), update(), etc. FWIW, current.update() is often misused in before/after business rules. If that doesn't yield any results, look for calls to getNextObjNumberPadded() (The global business rule that generates the next number.)

Finally, does this happen on other tables or just the story table?

[palmen]

There are no BR on the tables related to Stories using current.update()

I also did the same test in my Developer Instance (running Helsinki) where I haven't touched the SDLC module with the same result.

Created a story and filled in required field and pressed submit, after that clicking on Create New from Agile Development application and 1 number was skipped in the number serie. Did the test again but clicked on New button to create the second story and 2 numbers were skipped.

I've tried incident where the behaviour isn't the same in my dev instance and the other instance I'm working on.

[Chuck Tomasi]

Check client scripts as well. Someone may be doing something "off" somewhere there too.

[palmen]

All the Client Scripts are ootb, haven't touched them at all

[Chuck Tomasi]

Hi Fredrik,

I unable to reproduce this using Chrome and Safari as my two browsers on new Helsinki instance. I was also unable to reproduce it when using two Chrome windows/tabs (thinking it might be a session thing.)

I recommend reaching out to customer support on this one.

Is it happening on other tables or just stories?