The form title and form subtitle will appear at the top of the form as the page’s header and sub header (via the H1 and H2 HTML tags).
A form title is required. A form subtitle is optional.
Projects
At least one project must be specified indicating that submissions using this form will create issues in that project.
If multiple projects are selected then the form design must include the project field so the submitter can indicate which project to create the issue in. As projects are selected or unselected the values for the dropdowns in the field settings section will be refreshed to reflect the available options for all projects slected.
Only active projects can be selected (no disabled or read only projects).
If a project is deleted then the project is removed from the public form configuration. If the deleted project is the last project for the form then the delete will not be disallowed.
Field Settings
Field settings controls the initial Resolution, Status, and Assigned to User values of the issue created through the public form. Valid values for these choices are derived from the selected projects' workflows and project membership lists.
If multiple projects are selected and these projects use separate workflows then at least one Resolution State must be in common in each of the workflows. The resolution and status specified cannot be removed from the associated workflows using the workflow designer.
If multiple projects are selected only users that are members of all the projects will appear in the list of available users for "Assign to a specific user". The user ID specified cannot be deleted or marked disabled. If the user is renamed the rename will be propagated to the form definition.
Only groups that have a Team Lead specified for all projects selected will appear in the list of groups available for "Assign to team lead of group". The selected group cannot be deleted. If the group is renamed the rename will be propagated to the form definition.
Additional Field Settings
The additional field settings section allows default values to be specified for issue fields that do not appear on the form itself. The dropdown list on the left contains a list of all fields that can have default values set for them.
Use the controls to add or remove Additional Field Settings
All fields that do not have a default value set on the public form additional field settings will use the system defaults
If an issue field is deleted from RMTrack then the field is removed from the Additional Field Settings section of all public forms.
The different field types allow different default values to be specified:
Dropdown field values will be chosen from a list of the values defined for that dropdown. When the form is for more than one project, the values available for project dependent dropdowns will be restricted to only the values that exist in all projects selected. Dropdowns that are dependent on other dropdown fields cannot have defaults set and will use the system default.
Text and comment log type fields will accept any character string for the default.
Yes/No (checkbox) fields will present a dropdown containing a Checked or Not Checked value.
Numeric fields will accept a number only. Number of digits and decimal places, and whether negatives are allowed are controlled by the validation rules defined for the field.
Fields based on dates or date/time will show a text field. Values for setting dates can be:
controls to add or remove Additional Field Settings