IQTell ($4.16/month, but I do not recommend its use if calendar sync matters to you) Sync: One-and-a-half it looks like a two-way sync, but after an event has been synced, only changes in FT are pushed to Gcal, not the other way around.Android app: Yes (but easily the most ugly of them all).Sync: Subject-only body of appointment created in Gcal is lost on sync.Import: Technically, Evernote, but for bulk import it's unwieldy.Sync: Needs to be kicked off manually, and sync is subject-only but body of appointment created in GCal is retained in GCalL on sync.Sync: Full, but spotty, needs to be kicked off manually, support unresponsive.As it thus seems that hiTask is functional but essentially abandoned, I would not recommend storing anything of value here.ĭoit.im ($1.67/month, I do not recommend its use) HiTask purports to have an API (which means one could in theory implement import), but it doesn't work, and it is next to impossible to reach anyone in hiTask for questions of any kind. Import: Sort of - it can sync with gtasks, but I don't see a way to break that link, so when I turn of gtasks sync, the corresponding hitask tasks go away.Hitask (free, but I do not recommend its use) I'll probably find the next major (un)usability issue when I'm tempted to try it again in a few weeks. Buying pro doesn't help - without pro, the above isn't even possible. The visuals are great, but every time I try to move my work there (4 times so far) I end up spending hours of work to overcome the last roadblock only to find the next one, and then rage-quit. I'm trying to love this thing occasionally, but they really need to work on usability, not just the visuals. Oh, and there is no way to multi-select tasks to do bulk edits - everything is task-at-a-time, so moving these tasks is grindwork. To then find that there is no way to move groups between projects.Īnd while tasks within groups can be moved, you have to then manually regroup them. The UI slows to a crawl while doing this. Unless you go through the effort to split out all your tasks into projects, massage them into a format that DT will understand, and then one by one import these through, activate google tasks sync for the desired project, deactivate, lather, rinse, repeat. There is no task import, except via Google Tasks, so import is out. Bubble interface is fun if you have 10 tasks, and list interface clearly takes second seat to the bubble interface - no grouping, no filtering. I can not recommend it in its current state. Needs to work on the basics before it is actually usable. Also, moving tasks around in GCal through eM Client causes task duplicates on every change. Import: Google tasks, CSV (even if the format is a little funky)ĭownsides: the body of your tasks as they show up in Google Calendar has metadata in them, which you should not remove.Sync: Full, Instant, just make sure to leave the metadata in place.I do not count the existence of an iCalendar feed as sync - it is read-only on the GCal side, and updated irregularly. Many of the projects below will say "we have sync! Just use Zapier/IFTTT/etc", but that is invariably only one-way, create-only sync, so any update on either side and the registration will diverge, which makes sync sort of pointless. I am still actively testing the other options as they progress (or as new options become available) GQueues is basic but hits on all the required points, even if it isn't flawless. dan.g.One product consistently comes out on top: GQueues. If I understand correctly, JSON is pretty "standard" format for presenting tree structures, at least I've encountered it couple of times in export or import settings of tree task managers (here for example third-party developer offers export to JSON from Todoist service ) JSON export file contains a little bit of private information (email, etc.) so I edited it with Notepad++ (to post it here in public), hopefully I didn't break anything in structure. How specific tree is built from these I haven't figured out. For example, if "Task ID" number is located in first "ID" field, it belongs to top (root) level. The more levels tasklist has, the more "ID" fields are there. If I understand correctly (I'm not too smart), parent-child relationships are identified by amount of "ID" fields, and location of "Task ID" number (in specific column) indicates to what level task belongs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |