View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0025973 | mantisbt | custom fields | public | 2019-08-06 11:18 | 2019-08-20 10:17 |
Reporter | cproensa | Assigned To | cproensa | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | assigned | Resolution | open | ||
Product Version | 2.22.0 | ||||
Summary | 0025973: custom_field_set_value() does not apply $p_log_insert | ||||
Description | The parameter $p_log_insert: whether it create log entries for the value change | ||||
Tags | No tags attached. | ||||
removed from that PR |
|
I'm not so sure, see my note in the PR. |
|
This is @dregad note:
Being the lowest level entry point to update a custom field, i expected that the option to bypass history logs makes sense to be optional on both insert, and update, of the field value. |
|