View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003343 | mantisbt | bugtracker | public | 2003-09-08 11:19 | 2005-04-18 10:28 |
Reporter | hassan | Assigned To | vboctor | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Fixed in Version | 1.0.0a1 | ||||
Summary | 0003343: Manager cannot see Project after creating it as "Private". | ||||
Description | I've configured mantis as that Manager can create projects. On creation screen if project is set as "Private", after creation, the manager himself cannot see the same project in the project listing. So he cannot work any further to edit it and add more fields/members etc. in the project edit screen. | ||||
Additional Information | config_inc.php settings: Threshold needed to manage a project: edit projectdetails (not to add/delete projects), uploaddocumentation, ...etc.
Threshold needed to add/delete/modify news
Threshold required to delete a project
Threshold needed to create a new project
Threshold needed to be automatically included in private projects
Threshold needed to manage user access to a project
Threshold needed to manage user accounts
| ||||
Tags | No tags attached. | ||||
Mantis v0.18.0a4 |
|
The fix would be to add the creator of the project to the user list in case the project is private and the user is not an administrator. |
|
I'm looking at a similar problem here using Mantis 0.19.2: Although $g_private_project_threshold is set to DEVELOPER, neither MANAGERs nor DEVELOPERs are able to select private projects from any drop down listbox. Correct me if I'm wrong, but it looks like the function user_get_accessible_projects doesn't care about this option at all...? |
|
Replacing the line if ( user_is_administrator( $p_user_id ) ) { with if ( access_has_global_level( config_get( 'private_project_threshold' ) ) ) { in core/user_api.php solved the problem for me. |
|
That indeed seems to be the correct resolution. I just ran into this bug myself. :-) That also seems to be the only thing that is needed. The appropriate users are already added to the list of users in a project, it's just that the appropriate projects aren't added to to the list of projects a user has access to. |
|
Thanks - sad enough that nobody with CVS write access seems to care... |
|
Fixed in CVS. A more correct fix is: if ( access_has_global_level( config_get( 'private_project_threshold' ), $p_user_id ) ) { |
|