Understanding Issue Form Validation

Issue Form field definitions, whether or not a field is required, how it is initialized, valid values, and so on, are specified using the Schema Editor in the AccuRev GUI. As you work in an Issue Edit form, you may notice these effects:

• A new issue has values automatically filled in for certain fields.
• One or more fields have automatically been set to a specified value.
• The set of choices available in a list has changed.
• The set of required fields has changed. If a field's label appears in red, it is a required field. You cannot save the issue record until every required field has a value (that is, is not empty or in the case of lists, is set to a value other than <none selected>). Some required fields may have values set through an automated field initialization.

  If you attempt to save the issue record when one or more required fields lack a value, AccuRev displays a dialog box containing a list of the required fields. You must specify a value for all required fields before you can save the issue record.

• The Changes tab has become required. This validation option prevents an issue from being saved unless there are versions associated with the issue.
• One or more fields, tabs, or issues are read-only.
• Setting a field to a certain value requires a type of relationship to another issue. For example, setting State to Duplicate requires that you identify the issue that this one is a duplicate of.