Hello everyone. I've a doubt about sharing task lists at outlook 2010.
It is posible to see someone else's task list in our outlook task list?
Cause if it is, i can't figure it out. I will attach a photo onto this ticket so you can see for yourself what i meant.



- 1 - it's my task list
- 2 - it's where i want to see the shared task list (if possible).

Thnks in advance

Attached Images

shared task lists.jpg (95.9 KB, 13 views)

When a user shares their task list with you, confirm you have the proper permissions. All tasks will show on the right hand side by default. This is a common service for all Exchange accounts.

Based off your screen shot, it shows the one listed task. If you have no active tasks, they will not show in the list view. try testing this by creating a simple 'Test" and Test 1" tasks. Put one task in your task list and one in the shared task list.

Hope this helps.

First, thnks for you help.
second, the image i uploaded represents:
1 - my personal task list. and in that case there's no problem cause when i create a new task, immediately appears the new task on the task list (on the-right part of the screen);
2 - this represents the task list that someone is sharing with me. And the problem is i can't see it's tasks on the right screen, like mine. I can only see them on the middle screen. Even when i create a new task, they don't appear on the right-screen. I don't know if there's a solution for this.

Thnks again

Thank you for continue to provide updates.

On an Exchange service with Free/busy information activated, shared task should by default show on the right side. Our company has over 15 Employees all sharing tasks presented down from our Systems manager. However, sharing tasks is like sharing calendar. It requires the proper permissions.

I recommend removing the share task list and having the owner, even if it is you, remove the permissions and start over. Make sure you at least have an Editor level of permissions.

Additional research shows no command line switch or solution to this issue. This is infact a defualt function of Outlook in an Exchange environment.