In tracking which users are members of a project, we currently use
For public projects, all users are project members. Users access
rights may be changed by adding an entry to the project_user_list table.
For private projects, only those listed in the project_user_list
table are allowed, EXCEPT if the user's global access rights meet the
private_project_threshold. This exception causes a significant amount
of extra code and database queries to add these additional users.
I would like to propose that all project overrides, whether they
be access level changes, or project inclusion be stored in the
project_user_list table. This will simplify the database queries and
speed some things up. Additional related changes would include:
- an upgrade process to add grandfathered users to the
- a check when changing a user's access level to see whether they
should be added or deleted from private project membership
Glenn Henshaw Logical Outcome Ltd.
e: thraxisp@... w: http://www.logicaloutcome.ca
Mantis developer and user