Feature #5765
closed
Issue Numbers per Project
0%
Description
My suggestion would be add issue numbers that are specific to projects and not global. I know there are probably many of us that move from other systems and need to maintain ticket numbers across the transition. Ie, moving 2 projects that both start with issue #1. I'm guessing this would impact many aspects and possibly require not using the auto increment id field of the issues table but adding a new field (number or whatever) to the issue table.
Related issues
Updated by Moritz Voss over 14 years ago
Should be optional at best, IMHO.
Our shop has so many projects, and so many cross-project relations that pop up every now and then, we rely heavily on the opposite - unique ticket numbers, globally.
Updated by Mischa The Evil over 14 years ago
Updated by Felix Schäfer over 14 years ago
- Status changed from New to Closed
- Resolution set to Wont fix
This has already been discussed and won't be implemented.
Updated by Andriy Lesyuk about 10 years ago
Did this in the plugin (uses the project key, that gets prepended to the issue unmber). "Legacy" issue IDs can be still used.
Updated by Ramiz Raja Chaudhry about 9 years ago
Andriy Lesyuk wrote:
Did this in the plugin (uses the project key, that gets prepended to the issue unmber). "Legacy" issue IDs can be still used.
This plugin is highly unstable, I have used this plugin to one of the redmine(2.6) project and after removing so many bugs, it still has many. I would suggest to not to use this plugin at all.
Updated by Andriy Lesyuk about 9 years ago
Ramiz Raja Chaudhry wrote:
This plugin is highly unstable, I have used this plugin to one of the redmine(2.6) project and after removing so many bugs, it still has many. I would suggest to not to use this plugin at all.
You have bugs after removing it or when it is installed?.. Also, you should not use it for 2.6 as it does not support this version (the home page lists versions supported).