Assign more than one user to a ticket

The module was designed with the notion of only one person being assigned to the ticket at a time. That said, I don't think it would be overly difficult to enhance it to support assigning tickets to multiple people. Patches are welcome, otherwise I may look into this myself at some point.

I would also be very interested in assigning multiple users to a ticket for that case that the job involves more then one person. I took a look but "assigned" is all over the module so there is no way of doing it just like that without really knowing the whole module.

subscribe

I too would like to be able to subscribe a group, because subscribe only allows a certain number of characters in the field. Is there a way to subscribe A role?

@rjperry: I think that subscribing a role is not a problem - it is in the actions supply (send a mail to all users of a role). But I would like to set assigned users by creating each node (e.g., by userreference field). And that's a problem because (I think) rules are able to load only one user, even if the userreference field has multiple values.

I don't understand you message My-Family, can you explain a little more?

@rjperry: "Is there a way to subscribe A role?" - Yes: Triggered rules > Add a new role > you will set Label, Event, Condition (IF: not necessary) and Action: (DO): System: Send a mail to all users of a role. That's all.

But I need to specify users in the moment when I'm creating/updating the new node (in my case, Event is node created or updated). I'd like to specify users in userreference field of each node. So, the Action in rules is Load a referenced user and then send email... it works well, but only for 1 assigned user (only 1 or only the 1st value in the userreference field). The trouble is, if I need more assigned users. Possibly there would be also other ways (not necessarily user reference), but I have no idea....

I would like this as well

We will support this in the upcoming 7.x-2.x branch; I do not intend to implement it in the current 7.x-1.x branch. (A well-written and community tested patch would still be accepted, however)

Review if this is an option