05-09-2019 02:15 PM
05-09-2019 02:15 PM
Has anyone noticed that flagged emails and planner task get duplicated into your 'Tasks' List. Which when you complete the task in 'flagged email' or 'assigned to me' lists, do not get deleted from the 'tasks' list?? (They do get completed back in Outlook and planner though)
05-28-2019 12:31 AM - edited 05-28-2019 12:42 AM
@Malcolm FraserI believe I am seeing the same thing as of this week.
I have recurring tasks that I add to My Day. When I check off the task, it briefly goes away and then returns. The second time I mark it complete, it goes away completely.
Reviewing the tasks in Outlook, it only shows one instance of the task being completed.
Update: I switched to marking the items completed using the Outlook interface. It also marks the item completely briefly, and then resurrects the task. The second time it is completed, it stays completed. However, the task lists only shows a single instance of it being completed.
08-16-2019 11:02 AM
i have a similar problem.
when moving a flagged mail conversation to a group (like a customers - or waiting for feedback) i have 2 entries in Outlook. One of them is an empty task and one of them is the flagged mail. In my point of view there should be only the flagged mail in the task list of Outlook, as later on you want to respond to that item.
Also the categories from Outlook are not visible in To-Do. This would be a nice feature. Mostly a flagged mail has one categorie which states which customer or which area it belongs to and the other category is if i am waiting for a feedback or if I actually have to do something. So it would be good when tasks can belong to more than one group (as it is allowed by Outlook already).
Are these problems already known / the features are planned to implement?
10-13-2019 05:30 PM
@Luiz Siqueira Neto - Actually, I don't think I did anything. Sometime after I posted this, a update came out and the problem appeared to be resolved.
10-14-2019 05:42 AM
10-14-2019 06:22 AM
@Aksel Mjeldheimmy version is 2.2.1910.8006. Apparently the problem still persists.
10-16-2019 03:47 PM
10-18-2019 04:41 AM
Sorry for the delay - I've been on remote.
My desktop is using 2.2.22816.0