View Revisions: Issue #26573

Summary 0026573: Required custom field is not validated if not editable by the user
Revision 2020-01-07 18:54 by cproensa
Description

When a custom field is required on resolve/close, and a status change is made through bug_update_page, or bug_change_status_page
If the field is not editable by the user, the field is not validated to have a value according to the "requiered" flag.

For example:

  • custom field "required on resolve", and still has no value for the issue.
  • custom field have "write access" higher that current user level
  • Update from status "assigned" to "resolved" through bug_update_page or bug_change_status_page

After the issue update, the status is now within the resolved status threshold, but the custom field still has no value.

Revision 2020-01-07 18:47 by cproensa
Description

When a custom field is required on resolve/close, and a status change is made through bug_update_page, that custom field is not validated for existence.
For example:

  • custom field "required on resolve", and still has no value for the issue.
  • custom field have "write access" higher that current user level, so that its not shown in bug_update_page
  • the update modifies status from "assigned" to "resolved"

After the issue update, the status is now within the resolved status threshold, but the custom field still has no value.