Make 'New Ticket' default select options invalid

[tclugg@…]

I find it annoying that the new ticket submission provides defaults for drop-down ticket properties that may be incorrect, allowing a forgetful or inattentive user to submit a ticket with incorrect properties. This is especially annoying for small projects where nobody performs ticket triage, resulting in tickets being mis-filed and consequently not acted upon in a timely manner (eg: when developers are working at completing a particular milestone).

I would prefer that drop-down ticket properties default to "Please select..." or similar when creating a new ticket, forcing the user to review each property and select an appropriate value. This behavior should be configurable for each ticket property.

Related to: #1957, #2054, #4266.

[sid]

We have a similar problem, but I've dealt with it by setting many of the fields to blank values (like you see on t.e.o. for the Milestone and Version fields). In addition, new unassigned tickets are always assigned to a fake user. Then I use a custom query to search for tickets with missing values in certain fields, and I have another report that shows tickets from the last 30 days. Checking both of those reports once a week takes 10 minutes, and is an effective way to triage incoming tickets quickly.

[rblank]

As described above, the usual solution is to set empty default values (or use a string like "Please select...") and to perform some regular triage.

Enforcing explicit selections for all or some fields is covered by #2463.