X-2DOAPP-METADATA SHARE-SCOPE=GLOBAL:<2Do but the workaround shows: NC tasks app can (and currently does!) SUPPORT those parent-child-connection (I don´t know which technique is used by 2Do app when selecting "project" or "checklist"), but it doesn´t create it. Not the best user experience, cause it´s not consistent. As a workaround I created some "spare" or "template" checklists/projects (tasks able to have child tasks) with the 2Do app, being able to use (rename, move and !!! add sub tasks which permanently stick to their parents !!!) them with the NC tasks web app. It´s quite frustrating, having a great server/web app and a great endpoint app seeing both are not really working together. Vice versa I can create a lot of levels in NC tasks web app (tested to 5 levels), but those are not synced correctly as described in way " NC Tasks to 2Do". Adding sub tasks to sub tasks (3 levels) or more is not possible.
#Caldav not working on 2do app full#
View them in NC tasks web app: shown correctly with full hierarchy informationīut: the way " 2Do to NC Tasks" is limited to only 2 level hierarchies.2Do app: creating root tasks (type "project" or "checklist"), assigning sub tasks => 2 levels.The other way around is working great indeed: View them in 2Do app: all shown flat as root tasks, hierarchy information is lost.Sync those with 2Do app (iOS & Android).
NC tasks web app: creating root tasks, assigning sub tasks => 2 levels.I´m a bit confused on this different behaviour, now reading all your posts understanding why (every app seems to implement an own way of creating a sub-sub-task hierarchy).
0 kommentar(er)
