Custom field marked as required, but it isn't

[legalize]

I have a custom numeric field marked as required on report, but Mantis isn't enforcing the requirement.

This is working for fields that aren't numeric, but on numeric fields, mantis allows a bug to be reported without requiring it.

Is this a known issue? How do I configure this to work properly?

My current configuration:

Name: Found in Build
Possible values:
Default value:
Regular Expression:
Type: Numeric
Read access: Viewer
Write access: Viewer
Min length: 1
Max length: 6
Display only on advanced page: no
Display When Reporting Issues: yes
Display When Updating Issues: yes
Display When Resolving Issues: yes
Display When Closing Issues: yes
Required On Report: yes
Required On Update: no
Required On Resolve: no
Required On Close: no

[atrol]

Seems to be a bug (I can reproduce this even with 1.2.0rc2)
have a look at
http://www.mantisbt.org/bugs/view.php?id=10670

[legalize]

My workaround was to set the default value for the required custom number field to "REQUIRED", which of course isn't a valid number. This means that the bug report will be rejected until they change that value to a valid number.