Feature #13378
open
Custom fields Type Auto Number Increasing
Added by an an about 11 years ago.
Updated about 3 years ago.
Description
Dear Redmine Team,
How can I add a custom auto number field for a project:
Ex: Project 1, issue 1.
This is a custom field only but has an increasing & auto suggest number per project. We can change this number.
I think this will be a custom field and it will show a suggestion number.
Of course, it may be dupplicated if two issues are created in the same time or we move issue across projects.
I know my opinion is related to #5765, #282, #538, #1926, #3843, #7873, #8039
- Category set to Custom fields
Interesting, but how/when will the custom field number get incremented?
Hi,
It will get the largest number in project and plus one.
I think it just a default value and it can be change
or
if some one move a issue to another project, it will default get a newest number.
Sorry for my English
- Subject changed from Custom fields Type Auto Number Increasing to Custom fields Type Auto Number Increasing
+1
Thats great! I just created my planned Inventory module almost entirely by using Custom fields / Dedicated tracker / Dedicated statuses etc.
Only thing I'm missing is the auto-increment functionality, which will solve (almost) the rest.
Btw it can be done by new datatype or by adding "[x] Auti increment" checkbox to Integer datatype.
And of course, "[x] Unique" will be helpfull - goint to check tickets for this.
- Related to Feature #5009: Add an option to set a custom field as unique added
+1
This is fantastic idea.
We are using additional number as a customer facing issue id, would be great if this would be maintained automatically inside redmine (now we are manually assigning the number verifying that there is no conflict...).
Hi, i am thinking on install the Redmine Serial Number Field plugin in order to hava number for my projects.
If i install this plugin what happen with the previous projects?
Thnks!
Also available in: Atom
PDF
Updated by Toshi MARUYAMA 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by