Kirill Bondar 2/19/2009 11:59:56 AM We ran into a similar problem in TeamDesk.
Imagine the following situation. One user tries to create the entry and #255 is shown. Second user tries to do the same, #256 will be shown. First user cancels. Should second user's entry be saved under #256, or #255?
Or, second user saves #256, first user saves #255. Date #255 was created comes after #256 was created. Looks confusing, right?
When deleting the record, it is not deleted physically, but, instead, marked as deleted, with the timestamp and the user. Deleted records are only displayed in the Recycle Bin (you may find the link to the recycle bin under the tabs). From there you can recover deleted record back to normal state, or physically delete it. Or the record will be deleted automatically after 30 days.
This is another reason why the numbers can not be reused. The situation: record #255 is deleted and new record will reallocate #255. Then the user go to recycle bin and tries to recover deleted record. Double #255 entries, huh?
Currently, bugs are numbered across all licenses and the "holes" into a bug numbering are usual thing.
However, with a drop of project sharing and license isolation, we can come to separate numbering sequence per license. And then, I believe, all these questions will arise...
|