View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003919 | mantisbt | filters | public | 2004-06-08 07:05 | 2005-09-11 08:12 |
Reporter | ralfiii | Assigned To | thraxisp | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Summary | 0003919: Filter feedback. | ||||
Description | In the filter-panel another filter-checkbox This way a developer wouldn't see bug-reports where feedback from the reporter is required. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
I would like to move away from assumptions that certain statuses exist. Ideally, an installation of Mantis can have a completely different set of statuses that work in a completely user defined way. I think using the new advanced filters you can do this by selecting which statuses you want visible (using the multiple selection filtering). And since this will be something you use often, you can save the filtering and use it whenever you want. |
|
I think these assumptions are not THAT bad, because most installations will work the same way. Naturally a more flexible and open system is always good. However, I looked at the Matis-roadmap and into that FAQ, but I didn't find an estimated lauch data for the next release that could include the new filter handling. |
|
Also with the new version of Mantis this issue can't be solved satisfactory (our developers want to filter ONLY closed, resolved and feedback, Feedback-reports have to become visible again after a bugnote has been added) Attached are the changed files of Mantis V0.18.2 to achieve what I originally wanted. Maybe somebody can use this work. |
|
In 0.19.0a1, if you use advanced filters (go to filters page, then click Advanced Filters or you can set it as the default through the config), you can have multiple selection. So in this case you can decide which statuses you want to see, and the rest will be hidden. Does this achieve what you need? |
|
This issue has been resolved with the new filter-capabilities. Thanks! |
|
Fixed sometime in release 1.0.0... |
|