View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020883 | mantisbt | filters | public | 2016-05-06 17:57 | 2016-10-25 18:41 |
Reporter | cproensa | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Summary | 0020883: Request: remove filter view type | ||||
Description | This is a request for, as part of a possible filter redesign, removing the view_type (simple/advanced) feature as it is now. The usefulness of advanced view is to select multiple values from the possible values offered by the filter.
Additionally, the view mode flag seems to be a property that is carried on the request parameters, and not stored in the filter by itself. Ideally, the simple/advanced behaviour should be tied to each field, and stored as part of the filter, as a field property alongside the stored values. The configuration options for: default_simple, default_advanced, simple_only, etc... | ||||
Tags | No tags attached. | ||||
related to | 0016854 | new | Simplify the filter box at the top of the View Issues page |
I wonder if including this in the "filter sanitization" PR 862... I'd really like to get rid of the simple/advanced difference in filters
My proposal to remove this simple/advanced modes implies: 1) simple or multiple selection input is always available (for supported fields), and the user can choose to have a given field in multiple selection mode if requested 2) All fields are shown. This means "hide_status" and "project" are always useable and not treated differently from other fields. 3) "show_status" and "hide_status" are combined and as one single visible field. This can be presented as a two alternatives selection
4) A new property is added to indicate "search_subprojects", which instructs the filter whether to include subprojects of selected projects. This is presented as a secondary checkbox within the "project" field. This changes has some consequences: A) Filter relies in javascript capabitilies. The switching of filter fields between single and multiple cant be made in a friendly way with static pages. B) Remove configuration "view_filters", which can be: This will provide a more homogeneus filter treatment, as the behaviour of filter fields and values is definied with the data contained by the filter itself (in contrast, at presen, filter behavioir changes based on view-type) |
|