Project

General

Profile

Actions

Defect #33727

closed

Issue number has jumped from 1200 to 1500 and then to 5000

Added by Rene Graetz almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Hello,

we have a strange behavior.
Out issue/ticket number, jumped from 1200 to 5000.

We are using:

Environment:
RHO (Redmine) version 3.3.3.stable
Ruby version 2.3.5-p376 (2017-09-14) [x86_64-linux]
Rails version 4.2.7.1
Environment production
Database adapter Mysql2

Has anyone a clue how this can happen and how we can go back?

Actions #1

Updated by Holger Just over 3 years ago

  • Status changed from New to Closed

This might occur when you attempt to create a large number of issues in a single database transaction which is however not comitted but rolled back.

With Redmine, this commonly happens when you attempt to copy a project but some issues (or other elements) are not successfully copied (e.g. because of updated custom field constraints or opther data references which prevent a copied issue to be saved). All the data of the copied project are deleted after a failed copy attempt. The issue IDs however are not resetted. This is an effect of how MySQL handles automatic integer keys.

With that being said, you might be able to reset the next ID to a lower value as long as you have no current issues using a higher ID in your database. There are various guides on how to reset an AUTO_INCREMENT ID in MySQL. One can be found at https://stackoverflow.com/a/8923132/421705

Actions

Also available in: Atom PDF