Hi,
After digging to some extent, I found that the JavaScript function checkCustomFields()
defined in <eventum>/js/validation.js is quite different from that in v2.1.1. The
mandatory check for Custom Fields works in 2.1.1.
Since I am not a PHP / JavaScript / Smarty maven, could someone help me out please?
Thanks and rgds,
Watson
-----Original Message-----
From: Srivathsan, M IN BLR SISL [mailto:M.Srivathsan@stripped]
Sent: Sat, 30-May-2009 10:35
To: Eventum
Subject: Bug in Mandatory Custom fields
Hi,
Has any one of you encountered this problem? I created a few custom fields (drop-downs
with pre-defined values set through the tool itself) and also flagged them as "Required"
during creation. Now in my Create Issue form, even if I don't select a value in those
custom fields, I am still able to submit the new issue. I very much see the "mandatory"
indicator '*' against the field names. I feel that this is a bug.
Just wanted to check if there is a patch or solution already available or is it that I got
something wrong.
Thanks and rgds,
Watson
________________________________
Important notice: This e-mail and any attachment there to contains corporate proprietary
information. If you have received it by mistake, please notify us immediately by reply
e-mail and delete this e-mail and its attachments from your system.
Thank You.
Important notice: This e-mail and any attachment there to contains corporate proprietary
information. If you have received it by mistake, please notify us immediately by reply
e-mail and delete this e-mail and its attachments from your system.
Thank You.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.