View Issue Details

IDProjectCategoryView StatusLast Update
0026573mantisbtcustom fieldspublic2020-01-08 06:07
Reportercproensa Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version2.24.0 
Summary0026573: 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
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.

TagsNo tags attached.




2020-01-07 19:03

developer   ~0063386

Last edited: 2020-01-07 19:03

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.
When the user has write access, the status change throws an error for the required field value. This should happen in the same way even if the user has no write access. The aim is that this field is guaranteed to have a value when the issue reaches certain status.

"Required On Update"
Here we could be more more forgivable, so that if the changes does not imply a "resolve" or "close" threshold crossing, requiring a value after updating can be enforced only to those users that have write access to the field.

Let me know your opinions, to include the changes accordingly.



2020-01-08 06:07

developer   ~0063395

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.