Redmine

I'd vote no on this one, first it's kind of cumbersome to do due to autonumbering, on top of that it leads to a lot of problems (if I link to issue #100 and it gets deleted, when what would be 101 gets created, my link now links to the wrong issue).

I've seen requests like this for just about every auto-numbering system available, and all of them is really micromanagement. Don't want gaps ever? Don't delete tickets.

Don't want gaps ever? Don't delete tickets.

Simple case - user doubleclicks "create" on the issue page which leads to two tickets of which one can/has to be deleted.

Wojtek K. wrote:

Don't want gaps ever? Don't delete tickets.

Simple case - user doubleclicks "create" on the issue page which leads to two tickets of which one can/has to be deleted.

This should have been fixed in Redmine, double post should not happen anymore.

Still, case with issues submited by e-mail (i.e. spam filtering problem not working in 100%)

Wojtek K. wrote:

Don't want gaps ever? Don't delete tickets.

Simple case - user doubleclicks "create" on the issue page which leads to two tickets of which one can/has to be deleted.

Reject it as a duplicate, relate it to the duplicate ticket.

The main limitation is basically how all database systems have done auto-numbers since forever, the overhead of maintaining the empty slots gains you really nothing except database fragmentation and a warm and fuzzy feeling that you don't have "holes" in your auto-numbers.

Wojtek K. wrote:

Still, case with issues submited by e-mail (i.e. spam filtering problem not working in 100%)

Reject as invalid.

+1