Project

General

Profile

Actions

Feature #8039

closed

Start issues from 1 per project

Feature #8039: Start issues from 1 per project

Added by Aleksandar Pavic over 15 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
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 1 (0 open — 1 closed)

Is duplicate of Redmine - Feature #5765: Issue Numbers per ProjectClosedActions

Updated by Etienne Massip over 15 years ago Actions #1

  • Category set to Issues

Updated by Ivan Cenov over 15 years ago Actions #2

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?

Updated by Jean-Philippe Lang over 15 years ago Actions #3

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

Same as #5765.

Updated by Aleksandar Pavic over 15 years ago Actions #4

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.

Updated by Andriy Lesyuk about 12 years ago Actions #5

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

Actions

Also available in: PDF Atom