Project Management Permission
Categories
Component ID
Component name
Component type
Maintenance status
Development status
Component security advisory coverage
Component created
Component changed
Component body
Intend to replace all the permission handling that is carried out by PM Module.
Under Development.
Assumption.
1. There is only one single parent reference field.
2. User is Drupal user and not pmperson.
Requirement for testing.
1. A single entity reference field for referencing parent as discussed in #2115545: Recursive Field for Drupal PM.
2. Entity reference field for assigning users to task/ticket/project.
3. Entity reference field for assigning users as "Project Manager" for project
4. After creating respective fields in the content type configure 'admin/config/pm/pmperm'.
5. Visit admin/people/permissions and assign permission to respective roles, the new permissions are awailable
under "Project Management Permission".
6. Test and report error/suggestions at https://drupal.org/node/add/project-issue/pmperm
What doest work
1. PM Team, instead set the cardinality of the reference field to unlimited to assign more people.
2. The "belonged" permission is a work in progress. It should work if a entityreference field is set up in 'pmorganization' referencing a user.
Extras
1. Normal drupal nodes are also available under pm permissions
2. Its possible to remove normal/default permissions that drupal assigns to the nodes.
3. Just by adding relevant refeence fields to any nodes, you can extend pm permissions like "view if assigned", "edit if belonged to same organization" etc.
