View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0021825 | mantisbt | filters | public | 2016-10-25 19:09 | 2016-10-25 19:09 |
Reporter | cproensa | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Summary | 0021825: Filters should store only modified values | ||||
Description | Currently, a stored filter contains all the values, for all the properties. If any property was not specified by the user, it is saved with the default value (eg, "any") An inconvenience is also that we dont know which values were actually set by the user. Also, with current system, we don't know if a field with a defaulted value (eg: "any") was actually a value set explicitly by the user
So, the proposed feature serves as a clean up, but prepares the ground for future improvements. Note that in current filter treatment, and more refined in PR 862, filters don't need to have all the properties defined. The only implementation needed is not store garbage, and keep track of actual set values. Regarding the concept of default filter: | ||||
Tags | No tags attached. | ||||