Feature #8039

Start issues from 1 per project

Added by Aleksandar Pavic over 8 years ago. Updated about 5 years ago.

Status:ClosedStart date:2011-04-01
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:Duplicate

Description

Does not seem that anyone reported this feature, however I've started to use Redmine in pretty big company, and we have ~80 ongoing projects.

It would be better to have features/issues starting from 1 on each project, instead of for example 437, on a first project which is in totally different department.


Related issues

Duplicates Redmine - Feature #5765: Issue Numbers per Project Closed 2010-06-27

History

#1 Updated by Etienne Massip over 8 years ago

  • Category set to Issues

#2 Updated by Ivan Cenov over 8 years ago

What would happen when moving issues from one to another project:
Let there be P1 and P2, and there be issue_1 in both: P1i1, P2i1. What will be the identifier of P1i1 when it is moved to P2?

#3 Updated by Jean-Philippe Lang over 8 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

Same as #5765.

#4 Updated by Aleksandar Pavic over 8 years ago

Ivan Cenov wrote:

What would happen when moving issues from one to another project:
Let there be P1 and P2, and there be issue_1 in both: P1i1, P2i1. What will be the identifier of P1i1 when it is moved to P2?

Well I'd keep issue id as primary key in DB, but make them visible via second set of keys project & id, if issue is moved, than it would get new id.

#5 Updated by Andriy Lesyuk about 5 years ago

Just released the plugin, that can help you (it requires project key in addition to the issue number). Please try.

Also available in: Atom PDF