View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0019978 | mantisbt | filters | public | 2015-07-27 15:41 | 2016-01-19 15:25 |
Reporter | atrol | Assigned To | cproensa | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Product Version | 1.3.0-beta.2 | ||||
Target Version | 1.3.0-rc.1 | Fixed in Version | 1.3.0-rc.1 | ||
Summary | 0019978: Values not preserved on filter page | ||||
Description | Most of the values are not preserved when clicking the link to choose the value. | ||||
Steps To Reproduce | Goto "View Issues" page Expected behavior: Status "New" is selected | ||||
Tags | No tags attached. | ||||
I can confirm this behavior. I think this a blocking issue for 1.3 release. |
|
tried a fix: https://github.com/mantisbt/mantisbt/pull/665 this bug happens on all fields that are enumerations: status, resolution, severity, priority... in simple and advanced filter modes. |
|
MantisBT: master b8dcb52a 2015-10-23 12:19 Committer: dregad Details Diff |
print_enum_string_option_list() accepts array of values This function was originally defined to accept an integer as current value for the option list, so it gets defaulted. However, some places (e.g. filter fields) were calling the function with this parameter set as an array of one integer (or more, for multiselection option lists). Changed parameter to accept array, since the check_selected() function already accepts an array of values to check. Adding a check for the case $p_val is a single value to cast it to an int, because check_select() should be called in strict mode for enum keys anyways, and some callers may still pass a number as string. In the case of "array of int", the caller must ensure values are proper int type. Fixes 0019978 Reworded original commit message. Signed-off-by: Damien Regad <dregad@mantisbt.org> |
Affected Issues 0019978 |
|
mod - core/print_api.php | Diff File |