View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0025981 | mantisbt | other | public | 2019-08-08 14:50 | 2022-02-26 05:52 |
Reporter | jzero | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 2.21.1 | ||||
Fixed in Version | 2.25.0 | ||||
Summary | 0025981: Custom Field doesn't complete with {today} when closing or resolving | ||||
Description | Hello. Found this bug when trying to implement a closing date for tickets. The custom field works correctly when used for creating a ticket but not for closing or resolving. | ||||
Steps To Reproduce | Create Custom Field with
Close (or change status to resolved) a ticket. The custom field will be empty. Create a ticket, the custom field will appear with today date. | ||||
Tags | No tags attached. | ||||
I am seeing this behavior as well in 2.22.2. Are there any plans to fix? |
|
Can you please try this with >= 2.25.0 I believe this issue may have been fixed as a side effect of MantisBT master efd8d1fb (see 0027950) |
|
Yes, is fixed now (2.25.1) Thanks! |
|
Thanks for confirming! |
|
MantisBT: master efd8d1fb 2021-01-31 04:00 Details Diff |
Validate date custom fields default value format Prior to saving the custom field's definition, we try to convert the provided format to a date, and if that fails an error is thrown. This also removes the need to enclose the format within curly brackets (e.g. {tomorrow}); this is more user-friendly, and simplifies the code as the given value can be passed on as-is to DateTime transformation. Backwards-compatibility is maintained for now, but may be removed in a future release. Fixes 0027950, 0027956, 0027983 |
Affected Issues 0025981, 0027950, 0027956, 0027983 |
|
mod - core/cfdefs/cfdef_standard.php | Diff File | ||
mod - core/custom_field_api.php | Diff File | ||
mod - docbook/Admin_Guide/en-US/Customizing.xml | Diff File |