Redmine

Good suggestion. Perhaps allow a pattern to be applied to generate ticket numbers, e.g. YYYY###### and let the default be the way it is now (#######).

I am not sure if I understand this. Your sollution to long ticket numbers is to make them longer? so that they include year as part of this?

How about: YYYYMMDDHHmm###### for a ticket number? These definitelly would be simpler than just a sequential, lowest number form.

Kind regards

Zarooba Rozruba wrote:

I am not sure if I understand this. Your sollution to long ticket numbers is to make them longer? so that they include year as part of this?

How about: YYYYMMDDHHmm###### for a ticket number? These definitelly would be simpler than just a sequential, lowest number form.

Kind regards

The ticket id length will be longer, but more intuitive and easy to remember. The complete date pattern also is a good idea, but I think that is not necessary.

MV

-1

I'm really again. Actualy what you are sugestion is much longer numbers than actual ticket number. ANd for our workflow it's much more clear to see simple incrementing numbers, because it's easy to understand which tickets are newer. Suggested sollution goes against simlicity. A agree that it can be usefull for few of us, but not for a whole community.

The sollution can be a plugin, or some special custom field with calculation...

I think it's not a good idea and could cause technical problems.
What if, by some unknown problem, the server running Redmine lost the correct time.. We'd have duplicated ids for tickets and it would be a mess (bigger than the simply date problem).

And how many tickets by day do you produce? The Ubuntu tracker issue id, for example, is a 6 digit number yet, will take some years to get the 7th digit. It's not so hard to memorize.

-1. Not a good idea, because at many places (in wiki or notes or related issues) you would have written them as 'text'. If the issue number now changes - all those places will point to bogus or incorrect/misleading points!

How to change this format in the ID field in the issues table???