Defect #1626

2 characters identifier too short?

Added by Leandro Lucarella over 9 years ago. Updated over 8 years ago.

Status:ClosedStart date:2008-07-11
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Projects
Target version:0.8.1
Resolution:Fixed Affected version:0.7.2

Description

I have a project which name consist in 2 characters. I want to identify it with 2 characters too but Redmine fails creating it complaining about the identifier being too short (which is specified in the form). I can't understand why a project identifier can't be 2 (or even 1!) character long.

It's possible to change that validation?

Thanks!

redmine.identifier.patch Magnifier - Trivial patch (1.28 KB) Leandro Lucarella, 2008-07-11 23:09

redmine.identifier.patch Magnifier - Trivial patch (updated) (1.25 KB) Leandro Lucarella, 2008-07-11 23:11


Related issues

Related to Redmine - Defect #3073: Minimum identifier lenght should be 1 Closed 2009-03-30

History

#1 Updated by Leandro Lucarella over 9 years ago

I've attached a trivial patch against 0.7 svn branch that do the trick.

#2 Updated by Leandro Lucarella over 9 years ago

Ups! Broken patch attached, here is the correct one...

#3 Updated by Thomas Lecavelier about 9 years ago

you should introduce a test case about that patch.

#4 Updated by Leandro Lucarella about 9 years ago

I'm sorry, I'm not a RoRer nor a Rubyier, I managed to make the patch because it was trivial, but I have no idea of how to make a testecase for redmine.

I'll appreciate instructions or that somebody else do it.

Thank you

#5 Updated by Jean-Philippe Lang almost 9 years ago

  • Status changed from New to Closed
  • Target version set to 0.8.1
  • Resolution set to Fixed

r2221 lowers this limit to 2.

#6 Updated by Leandro Lucarella almost 9 years ago

Thanks!

May I ask why not to have a limit of 1?

#7 Updated by Leandro Lucarella over 8 years ago

  • Status changed from Closed to Reopened

I'm reopening the bug because I don't see any reason to set the limit to 2 instead of 1 (i.e. non-empty).

#8 Updated by Anonymous over 8 years ago

Please don't re-open bugs of a closed milestone. What you've done is mark the 0.8.1 milestone as 'open' again when it was closed again. I'd suggest opening a new ticket and reference this one from the new one.

#9 Updated by Leandro Lucarella over 8 years ago

Ok, I'm sorry, I just opened a new bug report (#3073). Unfortunately I can't re-close this one myself.

#10 Updated by Mischa The Evil over 8 years ago

  • Status changed from Reopened to Closed

As requested...

Also available in: Atom PDF