View Issue Details

IDProjectCategoryView StatusLast Update
0023318mantisbtcustom fieldspublic2019-05-22 15:41
Reportercproensa Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version2.7.0 
Summary0023318: Custom field required on update is not enforced when assigning with status change

When a custom field is configured as "required on update", the behaviour when going through bug_change_status_page, to change status, is to show all such required custom fields, and ensure they are not empty when submitting the changes.
However, when the "assign" action is used, and status is changed as a result (eg, by option auto_set_status_to_assigned), those required custom fields are not verified.

A proposal is:
When the assign action is performed through bug_update page, check:

  • if the action results in a status change
  • and custom fields exist with "required on update" option
  • (and possibly) any of those custom fields are currently empty
    Then redirect to bug_change_status_page with the corresponding properties prefilled (new status, assignee)
TagsNo tags attached.


related to 0023919 new Able to close defects,even though a custom field is marked as "Required on Close" but "Display on close" in turned off 


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2017-09-05 19:17 cproensa New Issue
2017-09-05 19:18 cproensa Description Updated View Revisions
2017-09-05 19:18 cproensa Description Updated View Revisions
2017-09-05 19:19 cproensa Description Updated View Revisions
2018-02-01 04:03 dregad Relationship added related to 0023919