View Issue Details

IDProjectCategoryView StatusLast Update
0020221mantisbtfilterspublic2023-03-13 12:27
Reportercproensa Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status newResolutionopen 
Product Version1.3.0-beta.3 
Summary0020221: filter selection list for users, should account for subprojects the same way as filter does

For a "simple" filter, the bugs listed are those belonging to selected project (or current project), and its subprojects
For an advanced filter, only the bugs in selected projects are listed (no recursive search)

When listing some fields, like reporter, handler, note_by, etc
this option list should contain all users (or items) valid for the same set of projects that is listed by the filter.

So, for example: the reporter field should list a combined set of reporters from current project and all the subprojects (if its a simple filter).
This is more noticeable when using private projects.

Probably, would make more sense to retrieve all existing users for that condition, from bug data directly, instead of building the list based on project and access levels (its a search after all).

TagsNo tags attached.


has duplicate 0032130 closeddregad If a user is disabled From Manage-Users, this user does not show up in the "reporter" list when filtering 
related to 0028123 closeddregad "Report" & "Monitored By" in Filters can only choose the administrator if we disable Mantis user to file new tickets 


There are no notes attached to this issue.