Start issues from 1 per project
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.
#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.