”required” field on our defect form cannot be made not ”required”
| ♥ 0 |
We are having a problem with our QC Defects "form" (when creating a defect) where one of our custom fields always shows up as "required". We have tried many times to stop this by check/unchecking the "required" box for the field in the Customize / Project Entities / Defects area for our specific custom field and it seems to do nothing.
Marked as spam
|
Posted by |
Private answer
GoBroncos, Check your Workflow scripts for the Defects Module Scripts / Bug_New script/method. There are many lines in this code spelling out behavior of each field on the ''form'' that comes up when you create a new defect (using the SetFieldApp function). Find your problem field (identified by BG_USER_xx, where xx is an integer), and look at the settings for it. The second true/false value should be ''False''. Check for more than one occurrence of the field - there will be one for each security ''group''. Save the code and apply changes, then get out of the project and go back in to check it. It is unexpected, but when you have ''form'' customization dictating how the fields behave on the form, it trumps the ''required'' behavior set on the entity. Marked as spam
 Posted by pt-barnum (Questions: 4, Answers: 509) Answered on November 14, 2012 4:00 pm
|