+ Add Question

Subtasks show up twice

U

In the "Tasks with no date" list, subtasks show up twice. Once under the parent task, and once by themselves. Is that intended?

- Dave

All responses

David Trey staff
Replied on Jun 27, 2011 - 12:33 UTC

Hello Dave,

if you mean tasks that have sub-tasks are being listed with a little arrow which allows you to open the list of their sub-tasks and these sub-tasks are being displayed again by themselves, then yes, that was intended.

This way you still have the option to check which tasks are assigned to a parent task, but you're also able to see them if you don't use it.

If you have a suggestion on how to display them, please let us know and we may consider it in future development.


Best regards,
David

U
Unknown
Replied on Jun 27, 2011 - 15:57 UTC

Hi David,

Perhaps you could add this as an option in the preferences? I think nesting the subtasks (and not having duplicates) would make it less overwhelming when looking at the total task list at a glance. Perhaps it's just me though. Interested to see what other people think.

- Dave

U
Unknown
Replied on Aug 20, 2011 - 11:58 UTC

Please add my vote for NOT displaying sub-tasks twice, first inside a parent task and then by itself in general lists. It is confusing at best and misleading at worst to see the same task listed twice. The whole point of creating an hierarchy is to split bigger items into smaller ones, not to have them duplicated and mixed together. No?

Also, if a parent task is checked off, shouldn't be all child task marked as completed too?

Can you PLEASE show this otherwise extremely useful feature some love?

Thank you very much!

(At least, as people suggested, it could be an option for those few snobby organizational purists among us).

M
Million
Replied on Jan 10, 2012 - 10:57 UTC

This same "feature" turned me off on toodledo. And I can say I am disappointed to see it here, too.

IMHO, it misses the whole point of subtasks/nesting. If not removed altogether, there should at least be a setting somewhere to de/active this feature.

Regards,

A
atom
Replied on Jul 18, 2012 - 10:33 UTC

How about display it only once, and let the user decide if he/she want to see it opened/closed.

This way you still have the option to check which tasks are assigned to a parent task, but you're also can hide it if YOU DON'T WAN'T TO SEE IT TWICE. It also spare you the lots of time, what you spend thinking about wtf is this, looking for bug reports, support, other solutions...

Thanks

MS
Melissa S premium
Replied on Nov 01, 2012 - 23:40 UTC

I would like to see this feature removed as well. It confused me for a while & I thought it was a bug.

David Trey staff
Replied on Nov 02, 2012 - 07:50 UTC

Hello Melissa,

Thank you for your feedback. You're welcome to add a request to our Votebox: http://todoist.com/Vote/

Please note that currently, if you query for today's tasks, you will see all today's tasks regardless of their indent level. Displaying sub-tasks only under their parent tasks would require showing you tasks that are not due today, but may only have one sub-task due today. On the other hand, displaying no sub-tasks if a task is a parent task, might let you think it's safe to complete it even though they might be other things to do before that.

We would greatly appreciate if you could suggest what solution would be the best for you - showing all parent and related sub-tasks even if only one of them meets the queried criteria or don't show that a task that does meet the criteria is a parent task if that's the case. We always try to understand how you're using our software so we can improve it so you're very welcome to let us know what you think would be the best solution for you.


Best regards,
David

MS
Melissa S premium
Replied on Nov 02, 2012 - 10:26 UTC

Thanks David. I understand your logic now. I posted in the Votebox with some suggestions. http://todoist.com/Vote/showProposal/578/

Thank you!!

RH
Robert Hassan premium
Replied on Sep 17, 2014 - 19:28 UTC

I'm new at Todoist andjust came across the double entry problem now... can someone post if there was a final resolution on this issue? Thank you ...