iPhone + Nextcloud Tasks: Subtasks missing in 2Do

HB-1 · November 17, 2025, 7:29am

I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)

on

Which general topic do you have

Dear all,

There is a long-standing issue with the iOS app “2Do” when used together with Nextcloud Tasks. Subtasks created in Nextcloud do not appear as hierarchical subtasks in 2Do, but only as flat tasks. The underlying reason is that Nextcloud stores task relationships according to the iCalendar standard (RFC 5545) using RELATED-TO, while 2Do does not evaluate this standard property and relies on its own proprietary metadata instead.

I have provided a detailed technical explanation and a full standards-based argument in the related GitHub issue:

github.com/nextcloud/tasks

[Feature Request] Support 2Do subtasks creation

opened 09:36AM - 19 Feb 20 UTC

raimund-schluessler

enhancement help wanted feature

_Originally posted by @bcutter in https://github.com/nextcloud/tasks/issues/23#i…ssuecomment-587783529_ 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). My experience: **[1] NC Tasks to 2Do:** 1) NC tasks web app: creating root tasks, assigning sub tasks => 2 levels 2) Sync those with 2Do app (iOS & Android) 3) View them in 2Do app: all shown flat as root tasks, hierarchy information is lost. **[2] 2Do to NC Tasks:** The other way around is working great indeed: 1) 2Do app: creating root tasks (type "project" or "checklist"), assigning sub tasks => 2 levels 2) Sync those with NC server 3) View them in NC tasks web app: shown correctly with full hierarchy information But: the way "[2] 2Do to NC Tasks" is limited to only 2 level hierarchies. Adding sub tasks to sub tasks (3 levels) or more is not possible. 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 "[1] NC Tasks to 2Do". It´s quite frustrating, having a great server/web app and a great endpoint app seeing both are not really working together. **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. Not the best user experience, cause it´s not consistent... :-) ...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.** That would be SO powerful!

If you are affected by this problem, you may consider opening a support ticket with the 2Do developers as well. More reports from users can help bring attention to the issue.

Kind regards