View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0026573||mantisbt||custom fields||public||2020-01-07 18:47||2020-01-08 06:07|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0026573: Required custom field is not validated if not editable by the user|
When a custom field is required on resolve/close, and a status change is made 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.
|Tags||No tags attached.|
I think the behavior should have two considerations:
Both "Required On Resolve" and "Required On Close" should be enforced even if the user don't have write access to the field.
"Required On Update"
Let me know your opinions, to include the changes accordingly.
I agree with your considerations, but I'm 100% sure about being "forgiving" in the required on update status. I believe that if a CF is required, then we should enforce that, period. But I see the usability perspective and understand the rationale for only requiring it for users who have the rights to actually update it. But in that case it definitely needs to be mandatory for everyone before status becomes >= resolved.
|2020-01-07 18:47||cproensa||New Issue|
|2020-01-07 18:54||cproensa||Summary||Required custom field is not validated after bug_update_page => Required custom field is not validated if not editable by the user|
|2020-01-07 18:54||cproensa||Description Updated||View Revisions|
|2020-01-07 19:03||cproensa||Note Added: 0063386|
|2020-01-07 19:03||cproensa||Note Edited: 0063386||View Revisions|
|2020-01-08 06:07||dregad||Note Added: 0063395|