Filtering under assignments
Page: 1
Recent posts in this topic
It would be very nice to have a filter under Assignments which filters via person responsible: this would give an admin the ability to list all the tasks from each individual that have not yet been completed... would have been a nice response to the person today who declared "I need something to do" and has 300 open tasks :P
Sorry, I don't see that... I'm only getting "person accessing the page... is responsible", which is fine for my tasks but doesn't let me sort someone else's... unless I log in as them...
Ilija Studen
on Apr 18. 2008. 12:53 pm
Ah, I misunderstood your request - this works only for logged user filter, not for selected users. We'll consider this for one of the next versions, but v1.1 is completely closed now. Nothing new will be added.
I really don't know how you assign task, but making sure that only people who are actually involved with a task are assigned would sort this thing out. We found that, although really handy, multiple assignments are not that much used. Usually it is one assignee who is responsible for the specific task plus subscribers.
I really don't know how you assign task, but making sure that only people who are actually involved with a task are assigned would sort this thing out. We found that, although really handy, multiple assignments are not that much used. Usually it is one assignee who is responsible for the specific task plus subscribers.
activeCollab team member
Ilija Studen:I really don't know how you assign task, but making sure that only people who are actually involved with a task are assigned would sort this thing out. We found that, although really handy, multiple assignments are not that much used. Usually it is one assignee who is responsible for the specific task plus subscribers.
I think the difficultly here is there is no way to subscribe individuals to a ticket, when creating it, except by assigning them. Generally, we want/need a larger group to receive the initial notification, with text, and this results in "over-assignment."
On the other hand, you could think of this as trying to assign three levels of permissions: ultimately responsible person, people who may be /are working on the ticket (involved), and just plain subscribers who need to read the chatter.
Point about 1.1 being closed taken, of course :P
