We're looking for a way to assign multiple persons to projcts/tasks/tickets.
We've tried using Teams, but it's not flexible enough, we found ourselves setting up a new team for each project.
We use Storm for poject and task management and we have the following entities:
- IT team which are assigned almost to every project (as a team)
- System Manager (not from IT) which must be assigned as well, and is a different person for each project
- IT Auditor (not from IT) which can be assigned to different projects (has read-only permissions on all projects) and might be a different person for each project.
I think there should be a way to "Add person" to the assignment field (like multiple field values in CCK).
This way we could build dynamic assignments for each project/task/ticket without having to manage the Teams so much.
Comments
We have a feature request in
We have a feature request in the system to do this - http://drupal.org/node/713954.
However, there is a fair bit that needs doing to Storm at the moment, and there isn't enough community help to get them done.
Have you started on this yet?
We have strong development capabilities, so if you have a written design or you can give some written notes here a a comment we can start digging on the issue.
That would be great,
That would be great, thanks.
The issue hasn't really been started on yet.
I'm happy to review a design if you like, although I suspect this won't be a big change.
We should carry on this conversation on the issue on d.o.
Multi assignment - Work plan
We have review all the aspects of person / team assignment to project / task / ticket and it seems the only use of that assignment is to identicate the assignee on the item's page.
Some pages uses the assignee field as a filter: storm/projects, storm/tasks, storm/tickets.
Please correct me if I'm wrong but we found no other reports or views associated to a person to display his/hers assigned content.
Our work plan would be:
1. Create new feature called "Storm ext. - multi assignment"
2. Create a view that returns nids for all relevant persons and teams in a current project.
3. Create one CCK node reference field that uses the view in #2 as input. Use multi select attribute.
4. Assign this CCK to project, task and ticked content types
5. use hook_formalter to manipulate the node-forms and turn storm assignee field to a value field ('#type' => 'value').
6. Build alternative page to list of (3) pages above and replace the called function (hook_menu_alter). The pages will be based on the existing one and we only change the mysql query to use new tables.
7. Extra - add views for my projects, my tasks, my tickets on user page
We would like to get comments and other toughs: would it covers the muli-assignment in full? will this solution align with the development plans of storm in the future?