Microsoft To Do

[Silther]

Plesse add support for Microsoft To Do.

[abaker]

I have started working on this, you can check out the latest commits for progress. Its probably 3-4 weeks away from alpha testing

[Silther]

Any news?

[abaker]

Sorry no more progress yet, been super busy at work and some other stuff 😞

[RokeJulianLockhart]

https://feedbackportal.microsoft.com/feedback/idea/bf1e6ca4-14b9-ed11-a81b-000d3a0450e3

[abaker]

I've tentatively picked this up again. Basic two way sync works for all of the easy stuff (due date, priority/stars, descriptions).

Reminders, subtasks, and attachments are probably going to take a lot of work.

[abaker]

Last night I found out that the Microsoft Graph API for patching recurring tasks is broken. After I spent a whole lot of time implementing recurring tasks support 😢

And, just like Google Tasks, the first party Microsoft To Do app uses a private API that doesn't have this bug 🙄

[RokeJulianLockhart]

Last night I found out that the Microsoft Graph API for patching recurring tasks is broken.

@abaker, does an official bug report exist? https://feedbackportal.microsoft.com/feedback/search/746f5230-3b1c-ec11-b6e7-0022481f8472?q=Recurring+tasks+Graph+API doesn't show anything relevantly useful.

[abaker]

No just this Q&A from a little over a year ago. So I have no problem creating a recurring task, but updating a task to add or modify recurrence fails

edit: it just occurred to me that the issue here is the patternedRecurrence.recurrenceRange, which provides recurrence end features that the soon-to-be-dead Outlook API supports, but Microsoft To Do doesn't (end after date or # of occurrences). If I just stop sending recurrenceRange then it works

[RokeJulianLockhart]

So, @abaker, is it worth one of us doing https://feedbackportal.microsoft.com/feedback/post/ citing https://learn.microsoft.com/en-us/answers/questions/806339/unable-to-patch-a-todo-task-with-a-recurrence-patt?source=docs then? I'd really like recurrent task support for Microsoft To Do in Tasks.org.

[abaker]

No I don't think that will be necessary, recurrence will be supported. The issue was that the graph API exposes a bunch of functionality that the official To Do apps don't support, and this recurrenceRange block (i.e. specifying when recurrence ends) was one of them. If I omit this block then the recurrencePattern works

I rewrote the recurrence picker in Compose for v13.5 so that it would be easier to hide the recurrence features that To Do doesn't support

[RokeJulianLockhart]

@abaker, https://github.com/tasks/tasks/issues/2011#issuecomment-1670245288

I rewrote the recurrence picker in Compose for v13.5 so that it would be easier to hide the recurrence features that To Do doesn't support

Shall the GUI expose to the user which features are unavailable when editing a task, like by greying them or with notices that they'll only be supported in the local database? I've encountered potentially unsupported features when synchronizing with Nextcloud and it's been problematic (if that's the cause) such as comments. This seems more important than those, so if not, would it be a good FR before To Do support is released?

[abaker]

If you're editing a Microsoft To Do task and you open the custom recurrence picker then:

• The 'Ends' section will be hidden
• If you select 'Monthly' then the drop down that lets you select 1st/2nd/3rd/4th/last weekday of the month will be hidden
• Minute and Hour frequencies will be hidden

It is confusing that the app supports fields that aren't supported by the sync service, but the app should make the user aware of these limitations rather than hide the fields. I'm hiding stuff in this case because To Do does have partial support for the feature.

[RokeJulianLockhart]

Yeah, hiding them is also fine for now. I didn't realize Tasks did that. Some kind of obvious indicator would communicate why better though, as you state. Thanks.