View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006105 | mantisbt | filters | public | 2005-08-10 05:17 | 2012-01-23 09:37 |
Reporter | jleuzinger | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 1.0.0rc1 | ||||
Summary | 0006105: Filter "reporter", "monitored" and "assigned to" does not include Members of Subprojects | ||||
Description | When I select "all projects" (--> access level viewer), I cannot filter for reporter, monitorers and handlers because the comboxes are empty (i.e. only list the administrators). I expect the filters should work like the category-filter, which also collects all of the subprojects. | ||||
Additional Information | By the way, same problem exist when I structure the projects by means of a parent "empty" project: I created an "empty" Project just for the purpose to hold 3 subprojects. | ||||
Tags | No tags attached. | ||||
I just experienced the same issue. We have a project "User Backlog" where some endusers can report issues on our tools. End-Users are allowed to report only in their project "User Backlog". When the issue is confirmed, it is moved from User Backlog to another project (the project of the tool the issue is related to), in order for the developers to solve the issue. So all the end-user accounts are created as "Viewer", and then they are assigned to the project "User Backlog" as "Reporter". Then when we want to filter all the issues reported by a certain reporter, we switch to "All Projects", but in the "Reporter:" filter the end-users names are not listed! NOK "All projects" includes "User Backlog", so when I want to filter on the reporters of all project, I expect to have also the reporters of local projects like "User Backlog". The filter does not behave here as expected, because they are not listed. It means I have no possibility to filter on them with the current implementation. Note: reproduced on Mantis 1.2.5. |
|
I just reproduced the issue jleuzinger is describing in his additional information on 1.2.1 and 1.2.8. Does anybody know what is causing this problem? |
|