Edgewall Software

Opened 9 years ago

Last modified 9 years ago

#8403 new enhancement

Encourage users to select meaningful values for 'required' fields

Reported by: ebray Owned by:
Priority: normal Milestone: next-major-releases
Component: ticket system Version: none
Severity: normal Keywords: mandatory field
Release Notes:
API Changes:


When an enum field, in particular, is marked as 'required', the blank option is removed from the select element, and the first option is selected by default, if no other default value is set.

The problem with this is that it often leads to users submitting tickets with those fields left in their default values. It doesn't force them to select a meaningful value.

A decent workaround is to have a catchall (like 'general' for the Component field) as the default value for the field. But I've had use cases where we want to make sure the user has paid some attention to the field. The desired behavior here would be to have something like 'Select a Component…' as the first option. If this option is selected when the form is submitted, a warning would be displayed, and the ticket would not be saved.

Attachments (0)

Change History (1)

comment:1 Changed 9 years ago by Christian Boos

Keywords: mandatory field added
Milestone: 0.13

Maybe we need a mandatory flag for the fields. If the value given is empty (and that could be the default), the field wouldn't validate.

It's just generalizing what we currently do for the summary, I think.

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set.
The owner will be changed from (none) to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.