Assign projects, tasks, and tickets to people

It would be great if they were notified of assignments also!

@tekad: I have used the notifications module - with the notifications_team module - to inform users of new tasks and subscribe them to the thread. It's "outside" of STORM but fits nicely into treating the tickets as nodes.

I second the need to assign tasks, etc to people. What use is an issue if you can't specify who is responsible for it?

I would love to be able to have tickets, tasks and projects assigned to people. This module rocks, the only thing that is missing is the ability to see who is working on what and assign to a person when something has been done or a question needs answered.

+1 for this feature. This is the single biggest thing that's keeping me from using this module.

+1 this isn't stopping us from using storm - but it sure as hell would be cool ;)

subscribe

There MUST be SOME way to do this. Someone please post something if I'm missing a thread somewhere. I second others' praise of the module. It seems like it's exactly what we need, but without an answer to this simple question, we can't use it. And, I for one, really want to use it.

...sigh.

@alexm - there are workarounds for this. since all parts of storm are nodes, you're able to customize those nodes using CCK fields to fit your needs. a user reference field could be used for example.

Thanks for the response. I just wanted to make sure there wasn't a "right" way to do it that I was missing. I have it set up now with user reference, so I'll just try to follow that through. Not sure if it'll work exactly the way I was hoping, but should be able to get it pretty close. Thanks again.

Combined #269070: Assigning person for the tickets generated into this issue.

Why not make a dependency on user reference and use the features allready existing?
Why not use Views for the lists? Storm could setup the views but the user could change it.

#392414: Assign projects, tasks, and tickets to people has been marked as a duplicate of this issue, followers of this thread may be interested in the patches posted there however.

This issue will be dealt with as part of the review of Storm Teammember at #380008: Development of Storm Teammember which will look at how people are handled in Storm.

could you please elaborate from the standpoint of a fresh installation of drupal 6.13 and only the storm module installed?
what CCK modules are needed?
short description of how to add the user reference field to a storm ticket node?

hoping to be able to use this module for our college's trouble ticket and project management package

@atmanning, this is being reviewed in #380008: Development of Storm Teammember, please use that issue to raise any ideas/requirements you have as it helps to concentrate efforts in one issue.

Adding tasks to Storm is very time consuming especially if you're added more than 200 task. Could there be an import function or a GRID add view (tabled format) that you can easily add the required fields for 100 tasks, then save the added tasks and it would save all 100 tasks to the database.

This would REALY make entering tasks easier.

Not sure if this is discussed in another node?

Cheers!

@KMAN, your post is nothing to do with this issue. It'd be better for you to search existing nodes and if you don't find a relevant issue to post a new one.

Best route would be to follow-up on #477850: Add support for Storm content types to node_import.module

If you want someone to have full access to a company add them to the team for that project. If you only want them to have access to specific tasks, add them to the team for a task. If you have already added someone to a project, then they have access to all tasks in the project. You can also add someone to the team for the company. Just be as specific or general as you like when adding team members.

Hope that helps

How do you connect teams to tasks? The only way I see of doing it is through projects (in version 6.x.1.26)

#20 seems to be based upon the old Storm Teammembers module. This has now been replaced by the new Storm Teams module, which significantly changes the way that the data is stored.

The old Storm Teammembers module allowed very granular storing of who was linked to which project/task/ticket - but this info was not used anywhere and did not link in to permissions!

The next step for the new Storm Teams module is to add in:
1) Ways to assign more fields to people or Teams
2) Hierarchical permissions.

Hope that clears it all up.

This issue is closed, but the best issue to look at currently is #595276: Assign to fields for tasks and tickets.