Defect #8317

Strip whitespace from integer custom field

Added by Gerry Hawkins over 7 years ago. Updated 6 days ago.

Status:ClosedStart date:2011-05-06
Priority:NormalDue date:
Assignee:Go MAEDA% Done:

0%

Category:Custom fields
Target version:3.3.9
Resolution:Fixed Affected version:

Description

In my custom field, which is an integer, if I enter "123 " it complains.
Can this be modified to strip trailing, and maybe leading?, white space?
I haven't testing the fields, like float, but suspect theymight have this issue as well.
(using 1.0.4 waiting for 1.2.0)

8317-strip-spaces-int-cf.diff Magnifier (1.34 KB) Go MAEDA, 2017-04-15 05:45


Related issues

Related to Redmine - Defect #9588: Text fields used for data entry should trim whitespace. Resolved 2011-11-16

Associated revisions

Revision 17625
Added by Go MAEDA 9 days ago

Strip whitespace from integer custom field (#8317).

Patch by Go MAEDA.

Revision 17627
Added by Go MAEDA 6 days ago

Merged r17625 from trunk to 3.4-stable (#8317).

Revision 17628
Added by Go MAEDA 6 days ago

Merged r17625 from trunk to 3.3-stable (#8317).

History

#1 Updated by Thomas Kohler almost 6 years ago

In my opinion this is more an feature request than an defect because the field work like expected.

#2 Updated by Go MAEDA over 1 year ago

I wrote a patch to fix this issue.
Float custom fields allow leading and trailing spaces. Integer custom fields should also behave in the same way for consistency.

#3 Updated by Go MAEDA over 1 year ago

  • Related to Defect #9588: Text fields used for data entry should trim whitespace. added

#4 Updated by Go MAEDA 9 days ago

  • Target version set to 4.0.0

#5 Updated by Go MAEDA 9 days ago

  • Target version changed from 4.0.0 to 4.1.0

#6 Updated by Go MAEDA 9 days ago

  • Subject changed from in integer custom fields white space is not stripped off the end to Strip whitespace from integer custom field
  • Status changed from New to Resolved
  • Assignee set to Go MAEDA
  • Priority changed from Low to Normal
  • Target version changed from 4.1.0 to 3.3.9
  • Resolution set to Fixed

Committed.

#7 Updated by Go MAEDA 6 days ago

  • Status changed from Resolved to Closed

Committed to the stable branches.

Also available in: Atom PDF