Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TW sync with caldav doesn't distinguish completed tasks #74

Open
guyjames opened this issue Mar 2, 2023 · 3 comments
Open

TW sync with caldav doesn't distinguish completed tasks #74

guyjames opened this issue Mar 2, 2023 · 3 comments

Comments

@guyjames
Copy link

guyjames commented Mar 2, 2023

I have tried to resolve this issue myself by trial and error and by looking through the Issues here but have not been able to.

I am syncing Taskwarrior with Nextcloud Tasks (caldav protocol).

Due to the previous takedown of freecinc.com which I was using before, I haven't used TW for over 30 days (this is relevant later).

The sync between TW and caldav works perfectly except that I am only able to sync --all tasks — this includes all completed tasks in TW, which then end up in my to do list, but without completed status, i.e. it is not passing their completed status along to caldav during the sync. Due to not having used TW in the last 30 days that filter is not useful either.

I have been able to hack my way around it by giving all pending tasks a tag of "pending" and then only syncing those, but this introduces another step into the process which I would rather not have to do. I generally don't assign projects or tags to tasks unless they specifically need one.

I tried deleting the completed.data file in the .task folder but this didn't help, the completed tasks still appeared in the final sync from somewhere else.

Any help is appreciated.

@saccarosium
Copy link
Contributor

Having the same issue here. But after some investigation turns pit it's probably a problem with how nextcloud integrates with caldav. On other application, like 2do, there is no isses (syncong with my nextcloud instance).

@bergercookie
Copy link
Owner

Hi both,

Thanks for reporting.
Yes, I'm aware of this issue.

In general the "sync only modified tasks of last 30 days" is quite restrictive and also doesn't work with cases like this. I'm looking to extend it in the next few weeks to allow for ranges and to allow for tasks with due dates instead of modified dates

@bertrand-benoit
Copy link

Any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants