Feature #15174: Issue ids aren't sequential - Redmine

Actions

Copy link

Feature #15174

closed

Issue ids aren't sequential

Added by Vincent Roye over 10 years ago. Updated over 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

Due date:

% Done:

Estimated time:

Resolution:

Wont fix

Description

Hi,

I know this is an issue that has been discussed a lot but I would like to know if something has been done.

Is there a way to sequentially increment issue ids even if I work on multiple projects on the same Redmine instance ?
I want my projects issues increment like that :
Project 1 : issue #1,#2,#3
Project 2 : issue #1,#2,#3

Why ? Because it's very easy for the developers to get confused with the current issue id attribution.

Thank you very much for your answers.

Actions

Copy link

Updated by Jan Niggemann (redmine.org team member) over 10 years ago

-1

Because it's very easy for the developers to get confused with the current issue id attribution.

Just the other way round, it would be a whole lot more confusing if issue ids weren't unique...

Actions

Copy link

Updated by Vincent Roye over 10 years ago

I agree with you Jan but if my client really wants a sequential id attribution, is there a way to make this happen ? A patch ?

Actions

Copy link

Updated by Jan Niggemann (redmine.org team member) over 10 years ago

Vincent Roye wrote:

I agree with you Jan but if my client really wants a sequential id attribution, is there a way to make this happen ? A patch ?

None that I'm aware of, the ids are at the heart of redmine...

Actions

Copy link

Updated by Andrey Anufrienko over 10 years ago

An issue can be moved between projects.
So the Id must be unique in my opinion.
If you need 'sequence' you can add custom field to handle it, but now you will have to enter values manually. It may be handled automatically if Feature #15177 would be implemented in some way.

Actions

Copy link