ToDoist Filters failing when adding multiple conditions

[rsalsbery]

As of this morning, it appears that the ToDoist Filters fail when multiple conditions are added to the filter. As long as there is only a single condition the Filter is selectable and will present data but as soon as you add multiple conditions the Filter fails to transfer to the DAKboard

Steps to replicate

• Create a filter on your ToDoist account
• Add more than one condition to the filter (Example "assigned to: Robert & !/Completed")
• Link account to DAKboard and through a ToDoist Block

Current workaround

• Use only single fields in the filter (Example "assigned to: Robert Salsbery")
• Use list items other than filters.

[Dan-Peck]

I looked into this a bit. Their API is returning back a 400 Bad Request from the query that retrieves the tasks for a selected filter similar to the one described above. The "query" part of the filter is pulled directly out of their "sync" API data, so it should be what they'd expect for it.

Out of curiosity, I tried a few other ways to issue the query. But they all continued to respond with 400. So, this seems to be on their end. I opened up a ticket with them about it to see if they have any insight into what is going wrong with this.

[iamfromit]

Also feeling this. Any update on the ticket opened with them? Anything Dakboard + ToDoist users can do to help get a resolution?

(edit: To add to that; is there a way I can replicate this with the request that dakboard cloud-platform sends? I don't see a similar problem with other authorized integrations however they may be interacting fundamentally different, so hard to figure this out on my own without cloud-platform backend logs or requests/responses to dissect)

[Dan-Peck]

Any update on the ticket opened with them?

Hello, @iamfromit ! Thanks for checking in on this effort! Apologies for the inconvenience, but we do appreciate your patience. Recently, it so happens that we have spent some time looking into a related Todoist issue that we have discovered as part of an Internal Issue (# 525) that we have open. That Issue has finished development and testing at this time and is awaiting release-approval, so it should be available soon. I believe the work done on that one may also solve this symptom!

I will make a note to update this Issue once that has been released so we can get a feel from folks whether it has helped.

[Dan-Peck]

Status Update:

The aforementioned internal issue has just released and improves handling of Todoist sync data. Please let us know if this corrects the behavior you were seeing or if you are still experiencing issues with this (and any specifics you can offer regarding the scenario) Thank you!