Closed TylerLaBree closed 2 weeks ago
I'm having the same issue, also editing events on planify seams to mess up my events on tasks.org
any idea @abaker
I noticed this is sort of a duplicate of https://github.com/alainm23/planify/issues/1221
I haven't heard of this before, but based on the first case it sounds like this is an issue in Planify. I'd guess that the second case happens after editing the task in Planify, then the RRULE syncs back to Tasks.org. Let me know if there is anything I can do to help
This is because Planify is reading the rrule value incorrectly, we are working to fix this.
NOTE: This could be a bug in Tasks.org, although I have decent reason to believe it's to do with Planify, since sometimes the bug only appears in Planify.
Describe the bug
Tasks that haven't been set to recur every year sometimes appear with this setting. The tasks in question are all made on Tasks.org, synced to the Nextcloud server, and then synced to Planify. Two different things will happen sometimes:
There is occasionally an end date present. Multiple lines in the ics file obtained from nextcloud contain RRULE (which I don't think is expected behavior).
To Reproduce
I have not been able to reproduce this bug while observing it, but it has occurred in the past few days, on up-to-date software (tasks.org, planify, and nextcloud)
Steps to reproduce the behavior:
Expected behavior
Recurring rules should match between tasks.org and planify, and they should not be changed without user input.
Desktop (please complete the following information):
Additional context
Case study 1
Planify task, with "every year" recursion present
Tasks.org task, with no recursion present
Ics file obtained from "Export" button on Nextcloud
Case Study 2
I don't remember adding anything about yearly recursion or 2037 in this task. It seems to have appeared from nowhere.
Planify task, with "every year" recursion present
Tasks.org task, with recursion present
Ics file obtained from "Export" button on Nextcloud