0015760: Closing a project by disallowing users to enter new messages causes "View Issues" filter "Reporter" only show admins - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0015760	mantisbt	filters	public	2013-04-16 06:47	2013-04-16 18:41

Reporter	Zazzarim	Assigned To
Priority	high	Severity	minor	Reproducibility	always
Status	confirmed	Resolution	open
Product Version	1.2.5

Summary	0015760: Closing a project by disallowing users to enter new messages causes "View Issues" filter "Reporter" only show admins
Description	I want to close a project for new issues. I removed the mark for entering new issues for reporters. But now the reporter can´t select and even show other reporters in "View Issues" filter field "Reporter". Reporter sollen keine neuen Meldungen mehr anlegen dürfen. Deshalb habe ich den entsprechenden Haken in der Verwaltung entfernt. Doch nun werden die Reporter unter Einträge anzeigen nicht länger angezeigt und die Reporter können nicht länger sehen, welche Meldungen ein anderer Reporter erfasst hat.
Additional Information	Is there an other way to stop reporters from entering issues to a project? The project must be active because the current entered issues have to be resolved.
Tags	No tags attached.

atrol 2013-04-16 16:02 developer ~0036616	Reproduced using version 1.2.15

dregad 2013-04-16 18:41 developer ~0036622	This problem stems from the fact that list is built based on access levels / workflow permissions. While this logic makes sense in some cases, for filters it would make more sense to build the list based on actual data. In fact, this had already been flagged as an issue in the code, back in 2005 :O [1]. The obvious solution would be to build the list as a select distinct of users who reported issues in the project, but we need to be very careful about all places where this function is used to ensure this causes no regression, as well as trying to make this change as generic as possible so that the logic can be applied to other scenarios also. In other words, not an easy fix. [1] https://github.com/mantisbt/mantisbt/blob/2384d299/core/print_api.php#L284