0014358: Possible to avoid entering required custom field value using the 'assign to' button

ID	Project	Category	View Status	Date Submitted	Last Update
0014358	mantisbt	bugtracker	public	2012-06-06 11:20	2012-06-06 11:23

Reporter	vincent_sels	Assigned To
Priority	normal	Severity	minor	Reproducibility	always
Status	new	Resolution	open
Product Version	1.2.8

Summary	0014358: Possible to avoid entering required custom field value using the 'assign to' button
Description	When a custom field is marked as 'Required on update', this field will be displayed (and marked as required) when you go to the 'update bug page', or when you use the 'change status to' button. When you use the 'assign to' button, however, you are not asked to fill in these required fields - even though the bug is, in fact, updated. We have a mandatory custom field that we do not want the reporter to enter, but that we want our developers to fill in as soon as they do anything with the ticket. When a developer uses the 'assign to' button, he can avoid filling in that required custom field. As a workaround, I removed the 'assign to:' button completely, so the developers are obliged to use the 'change status to' button instead. To properly solve this, I see two possible options: Either include an intermediary page where the required fields are presented if required and empty Only show the button when all required fields have already been entered. Your thoughts ?
Steps To Reproduce	Assumptions: $g_auto_set_status_to_assigned = ON; Users have sufficient rights Steps: Create custom field Mark as 'Required on update' Assign custom field to a project Create bug in this project Use the 'assign to' button to change the status to 'assigned' and assign it to a developer. Result: The 'required custom field' is still blank, even though the status was changed and the bug is assigned.
Tags	No tags attached.

View Issue Details

Activities

vincent_sels 2012-06-06 11:23 reporter ~0032030	This also applies to required plugin fields, which currently also isn't supported using the 'change status to' button, as reported in ticket 0014329.