You are not logged in.
In the task all team members are of equal role. Why not the approach to be used such as in tockets (req, watc, assign, validator)? It doesn´t correspond fully to RACI matrix, but it is better then nothing. Also the roles in projects are poor!
Also the PMI or similar best practice for project members roles can be consulted: init, coord, superv, approver, assistant etc.
Last edited by madjaric (2015-04-05 11:17:59)
Miro
Offline
This shotrtcoming makes tasks practically unusable for serious projects (where the team member roles are scurtinized)!
Miro
Offline
GLPI try to intégrate a simple project management system.
If you want a real complex one, use a specific tool.
It is the same trouble for the reservation management for example.
MoYo - Julien Dombre - Association INDEPNET
Contribute to GLPI : Support Contribute References Freshmeat
Offline
Here I disagree strongly: GLPI has powerful infrastructure for PM. If you have decent user roles in tickets, there is absolutely no reason not to reuse the same logic in projects and in tasks!
This is a MUST: roles in tasks are simplest possible functionalities!
Without roles (possibly according to RACI concept) , the tasks are unusable!
Miro
Offline