View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003692 | mantisbt | bugtracker | public | 2004-03-27 10:14 | 2017-09-03 05:31 |
Reporter | hacker | Assigned To | atrol | ||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Linux | OS | Debian | OS Version | 2.6.4 kernel |
Product Version | 0.18.2 | ||||
Summary | 0003692: Restrict manage project view to everything above reporter | ||||
Description | We have 928 users in our system currently, and when going to Manage Projects, the userlist at the bottom can take a VERY long time to draw. This small fix, changes that view to ONLY display people above the access level of REPORTER. There is no real need to show Reporters in the Manage view, because the real goal is to show people who are subscribed to that project, or are developers on that project. By default, ALL users have access, so that is redundant. | ||||
Additional Information | At the bottom of manage_proj_edit_page.php, there is a function which derives this userlist. Simply change that $t_users assignment to match the following: $t_users = project_get_all_user_rows( $f_project_id, $f_access_level=DEVELOPER ); (i.e. add the second parameter to force it to display users with the access of DEVELOPER and above). In our case, this makes the system MUCH more responsive when managing large projects. | ||||
Tags | No tags attached. | ||||
This is still an issue in 1.0.3, and I always end up patching this fix in. We have 1,078 reporting and monitoring users in our tracker, so this list is VERY long, if run with the defaults. Here's the fix: --- /src/compiling/mantis-1.0.3/manage_proj_edit_page.php 2005-12-31 21:58:50.000000000 -0500
|
|
I tried with version 2.5.1 and about 36500 users. We are resolving this issue as "no change required", because it was reported against an old version of MantisBT which is no longer supported. We recommend that you upgrade to the latest stable version [1]; if after doing so the problem still exists, do not hesitate to reopen the issue. |
|