Hi.
Strange TU behavior.
I've started to use TU synced with toodledo.
In TU my tasks had parent/child structure more than two levels allowed by Toodedlo.
So I rearranged the tasks in order to match two levels only.
When syncing, a message regarding missing tasks id appeared.
I synced again and then all tasks disappeared from TU + Toodledo.
I think it is related to the different tree structure each software allows, being TU much more flexible on that, including adding subfolders and so on.
But if the user set TU to sync with Toodedlo, TU should constrain its expanded features to match toodledo structure. I mean, if I want I can create sub folders and big tree tasks, but it certainly will conflict with toodledo and cause trouble, as in my case a big missing tasks trouble!
In short, I suggest TU constrain its behaviour to match toodledo when syncing plugin is working, otherwise, if the plugin is disabled TU would work with full capabilities.
Best!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, I don't know what happened but both structures are working fine together.
At least, no one ever reported a problem about it.
If you create multiple sub-levels in TU, TU will sync these sub-sub-...-tasks as sub-tasks in Toodledo (one level) and keep the real structure somewhere else.
Folders, contexts, goals... sub-levels are not synced with Toodledo. If you reset TU, you will loose these sub-levels.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
Strange TU behavior.
I've started to use TU synced with toodledo.
In TU my tasks had parent/child structure more than two levels allowed by Toodedlo.
So I rearranged the tasks in order to match two levels only.
When syncing, a message regarding missing tasks id appeared.
I synced again and then all tasks disappeared from TU + Toodledo.
I think it is related to the different tree structure each software allows, being TU much more flexible on that, including adding subfolders and so on.
But if the user set TU to sync with Toodedlo, TU should constrain its expanded features to match toodledo structure. I mean, if I want I can create sub folders and big tree tasks, but it certainly will conflict with toodledo and cause trouble, as in my case a big missing tasks trouble!
In short, I suggest TU constrain its behaviour to match toodledo when syncing plugin is working, otherwise, if the plugin is disabled TU would work with full capabilities.
Best!
Well, I don't know what happened but both structures are working fine together.
At least, no one ever reported a problem about it.
If you create multiple sub-levels in TU, TU will sync these sub-sub-...-tasks as sub-tasks in Toodledo (one level) and keep the real structure somewhere else.
Folders, contexts, goals... sub-levels are not synced with Toodledo. If you reset TU, you will loose these sub-levels.