View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008900 | mantisbt | public | 2008-02-16 17:52 | 2009-05-19 19:47 | |
Reporter | smig1o | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Platform | LAPP | OS | Linux | OS Version | 2.6.24 |
Product Version | 1.1.1 | ||||
Summary | 0008900: Problems with project_get_all_user_rows - not all users are processed | ||||
Description | project_get_all_user_rows gives list of all users with level equal to or higher than given that eather members of project with given level or NOT in the project at all. | ||||
Steps To Reproduce | Put users into mantis with global level: X - developer Create project and put users with level now call project_get_all_user_rows( project_id, MANAGER ) SELECT id, username, realname, access_level and put results into $t_users array then you search all users assigned to the project: SELECT u.id, u.username, u.realname, l.access_level then you unsetting from t_users elements that didnt meet criteria on 2nd list. Global Users: A - manager Local Users: On both lists there is A and B user so X,Y,Z wont appear on output. Is that correct?? | ||||
Tags | No tags attached. | ||||
Seems a new array instead of unsetting values on old one is good solution for that. |
|
I believe that this is correct. For public projects, the global settings will also apply. For private projects, only the users listed in the project will be used. The best way to use this is to give users the minimum permissions globally, then upgrade permissions on a project basis. |
|
Ok.. I see. |
|