Assigning a task to a shared person
For more collaborative use, the task should be assigned to a shared person when creating each task.
User should be notified when a change is made for any task the user is assigned to.
-
Erich, so far we don't have such plans. I think that a single person should have a responsibility for a task.
If you think about this in the context of notifications - we're going to provide a way to supplement daily digest notifications for a list with instant notifications.
-
Erich Erich commented
Thats a cool feature, but du you plan, to make it possible to assign one task to multiple people?
-
J R commented
This is a great addition. So far testing looks great. How nice to be able to see everything on MY plate that is due today in ONE list, all nicely organized. THANKS!
-
Neil, actually, not everything in Checkvist are tasks. In many cases it is used to collect some information, organize thoughts, make notes on a conference talk, etc.
Having said that, I don't think it is a good idea to have an "assignee" for every task.
-
Neil Bowers commented
Here's my thoughts on what I'd like with respect to assigning tasks to a shared person:
If I create a list and don't share it, then the list has me as the owner, and any tasks created in it are assigned to me
I can share one of my lists with someone, and give them task creating ability. Any tasks they create are still assigned to me.
I can share a list with someone, and given them joint ownership. We can specify default task ownership. If that isn't specified, then when you create tasks, they're assigne
d to whoever created them. This might be a configurable option: some people might want behaviour where you can have no default assignee, and creating tasks without an assig
nee would result in unassigned tasks. Personally I'd go with the "every task has an assignee" model.
When creating a task, you specify who it should be assigned to, for example:
Organise travel insurance @neilb
When looking at a list, if it has a default assignee specified, then the assignee would only be shown for tasks that are assigned to someone other than the default.
If a task doesn't have a default assignee, then every task that has an assignee specified would have the assignee shown when listing tasks. -
J R commented
Thanks Kirill, I'm glad I could be of help. Can't wait for this update!
-
@JR, thanks a lot, your feedback is really valuable. This time we understood each other correctly, I believe. I don't think we'll release 'NOT' support in the filter, but proper filtering of Due page with regard to assignees will be implemented. Back to coding :)
-
J R commented
Thanks for clarifying @ vs #. That makes sense. The email notification isn't critical for me, but it could be for others.
And - you're right, only the @myusername tasks that are due should appear on the due screen, not ALL of the @myusername tasks. Sorry for that confusion!
I think what you're describing will do it. To be sure - here's an example
sharedlist1
task1 @myusername due today
task2 @someoneelse due today
non-sharedlist
task3 due today
task4 due todayThe due list should show task1, task3, and task4. It should not show task2 because it is not mine. (However as you said, a manager might want to see both - but the manager could see that by viewing the sharedlist1 anyway.)
Another thought - if the filters had the NOT feature available, I could go to the Due Lists view and filter with NOT @someoneelse and I would get just my tasks. But in large groups with many people, I guess this could become cumbersome.
Thanks for listening! -
@JR Actually, the most noticeable difference from tags would be e-mail notifications to assignee.
I've re-read your offer regarding changes on Due page and it really makes sense. Probably, there should be an option, whether I want to see due tasks assigned to different people (because I'm a manager who want to see overdue tasks of other people, for instance).
But, I still don't see a reason to show all your tasks with @username to appear on Due screen. When you're assigned a task, you can add due date to the task and this way the task will appear on your due screen.
Still, if you want to see everything assigned to you, you can use search.What do you think?
-
J R commented
Maybe it would clarify what you're planning if you could explain how this would be different from #tags. It sounds exactly the same to me so I must be missing something :-)
-
J R commented
For me, it's important to be able to see just my tasks, but ALL of my tasks. Using the @username makes sense on shared lists. But on unshared lists it doesn't make sense to use the @username (too much extra entry!) And so, on the due tasks view there would be no way to see all of my tasks, and just my tasks. If I filter by @username, I wouldn't see my tasks from non-shared lists. If I don't filter by @username then I would see tasks from shared lists which are not mine.
It seems like it will work fine within a single list, but not when trying to see all tasks. Or maybe I'm just not understanding how I would see all of my tasks at once, but just my tasks.
-
@JR I don't think we should show assigned tasks on the Due screen. We're going to provide @username syntax for list filtering/search (the same way as we already do for #tags). And, when we'll implement saved searches, you'll be able to create searches you need.
-
J R commented
Using @username sounds like a good way assign to a person
Ideas for function:
- when viewing the shared list, everyone sees all tasks unless the list is filtered
- when viewing my own "due tasks" view, I should see all my due tasks from my private lists, plus items from shared lists which have my @username, PLUS any items from shared lists with NO @username (meaning they are assigned to anyone on the shared list team.)
- the same should apply to any "filter all lists" result
- although I fear this will slow it down too much.... :-( -
Eric, I think that Checkvist will parse @username format only at the end of the task. So if you'll have @something in the middle, it won't be parsed (the same way as #tags work)
-
Eric Miller commented
Hey Kirill. The only thing that I want to mention is that I often copy / paste tweets into CV, so in comes the @handles mentioned in the tweet. Can CV ignore those as not an @assigned-user in CV?
-
Ted Pearlman commented
+1
-
@leshchenko Thanks! Actually, we thought that @assigned-user will get notifications about all changes in the task, without need to press "Notify about changes".
Filtering, autocompletion, search should definitely work. -
leshchenko commented
@user tag - yes
Notification "you've been assigned a task" - only by "notify about changes" link, no need for anything special
Filtering by @user tag - yes
Automatic sharing - no, lists should be explicitly shared to avoid accidental sharing of lists
Extra status - no
Autocompletion - yes
Assignee info - only in status if assignment was the last event on the task -
cmh commented
Are there plans to support the @user functionality mentioned below. It would be useful to have user tags which are separate from regular tags.
-
Merante commented
This is the only feature that is keeping me deploying this list throughout my whole business. We run everything via checklists and some projects have some parts of the checklist that are assigned to different team members. It would really help us to be able to track the progress of a project by keeping us alerted to who is finished with what.
I am ok with a work-around like tagging, but I would want an email sent to the teammate who is assigned the task when it is assigned.