0006104: Filtering private issues: behavior depending on access level - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0006104	mantisbt	filters	public	2005-08-10 04:11	2005-09-11 08:12

Reporter	jleuzinger	Assigned To	thraxisp
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	1.0.0rc1
Fixed in Version	1.0.0rc2

Summary	0006104: Filtering private issues: behavior depending on access level
Description	Filtering private issues has a strange behavior depending on the access level: Current access level >= $g_private_bug_threshold: Filter works correct Current access level < $g_private_bug_threshold: Filter has no effect I would expect that I won't see any issues when I set the filter to "private" in the second case. instead all issues are listed (as if the filter is set to "all").
Tags	No tags attached.
Attached Files	as_admin.png (25,635 bytes) as_admin.png (25,635 bytes) as_viewer.png (30,481 bytes) as_viewer.png (30,481 bytes)

thraxisp 2005-08-10 13:30 reporter ~0011147	Could you describe the filter you are using? The listing of private/public should be independent of other filters.

jleuzinger 2005-08-11 05:37 reporter ~0011161	Let's make an example (see also the 2 screenshots): I created (as admin) 2 Bugs: Bug A is set to public and Bug B is set to private. As an administrator I'm allowed to view the two bugs. Also the filter "View Status" works correct. As a viewer I'm not allowed to view private bugs and only public bugs are listed (which works correct). But when I set the filter "View Status" to PRIVATE, all PUBLIC bugs are listed. I would expect an empty list in this case.

thraxisp 2005-08-11 12:22 reporter ~0011171	Fixed in CVS. The filter now displays only the private issues originated by the user when the view state is set to private, and the viewer is below the private_bug_threshold. core/filter_api.php -> 1.121