Task Hierarchies

[thraidh]

Problem Statement

I have a project with many topics and services. When translating the customer requirements into tasks, I usually go top-down, which leads to tasks like this:

• ...
• connectivity
  • vpn server
    • automatic certification
    • handle client certification
    • forwarding rules
      • rule 1
      • rule 2
      • rule 3
  • vpn client
    • automatic certification
    • automatic reconnection
    • OS integration/autostart
• ...

Currently it is not possible to do something like that in Super Productivity in a satisfactory way.

❔ Possible Solution

Tasks can be handled as they are today, but visually tied together, i.e. by just indenting child tasks. Optionally you could show/hide child tasks.

⤴️ Describe alternatives you've considered

Today there are several unsatisfactory ways to approximate the functionality:

• Convert super tasks into their own projects: unsatisfactory, because they are not standalone projects, just part of a bigger project
• Name tasks like "Connectivity / VPN Server / Forwarding Rules / Rule 1": unsatisfactory, because the tasks belonging together are now totally independent and it is not possible to limit your focus on e.g. only "VPN Server"
• Convert some tasks into sub tasks as available today: unsatisfactory, because it is unclear where to make the split and it would still be necessary to name tasks and or subtasks with "/"-notation
• Name tasks after the leaf name only and add tags like #connectivity, #vpnserver, #automaticcertification: unsatisfactory, since #automaticcertification appears in VPN client and server and denotes different tasks
• Use tags like #connectivity_vpnserver_automaticcertification: unsatisfactory, because of long names and essentially every task would get its own tag, which is probably not the intended way to use tags
• Only use 2 levels and try to remember the lower levels or use another tool/text file to keep track of those tasks: unsatisfactory, because I have already a tool which does almost everything I need
• Don't use Super Productivity for complex projects: unsatisfactory, because I like Super Productivity and working on complex projects is my job

[github-actions]

Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!

[github-actions]

Hello there thraidh! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀

For more open ended discussions and/or specific questions, please visit the discussions page. 💖

[johannesjo]

Related #643

[thraidh]

Thanks for considering! Is there any way I can help?

[johannesjo]

As mentioned in the related issue this is currently not planned (though I am open for good suggestions on how to integrate deeper levels of sub tasks). As mentioned in the issue there is also the possibility to use the task description for deeper levels of planning:

- Something /
- Comet Haley /
   - Sub sub sub task /

[github-actions]

This issue has not received any updates in 90 days. Please comment, if this still relevant!

[Korne127]

I think this feature is essential as well.
I found this project and it really looks great, but being able to nest tasks recursively (and maybe even projects) is a necessary feature to organise your tasks imo.
I hope this will be implemented at some point, but for now I have to look for an alternative.

I also don't get why #643 has been closed when it's not yet implemented.

[RokeJulianLockhart]

@johannesjo, why do #2657 (comment) yet not reopen this?

[johannesjo]

My argument remains the same as with #643 (and so do the options to work around this). On the main view there would be very many complications UI wise to implement an infinite number of levels. Even a third level is difficult. There are also many problems with that conceptually that would need to be solved.

I am not ruling this out completely, but there is much work to be done (not sure when I will find the time...) and there is the risk that the end result will feel complicated for the end user.

As a general remark: I think super productivity works best as a tool to plan and engage with your tasks on a daily basis. Personally I use pen & paper or an empty text document for broader conceptual long term planning and transfer it as needed.

[github-actions]

This issue has not received any updates in 90 days. Please comment, if this still relevant!

[sunnylake180]

I love the app thanks so much for making it!
Is drag and drop the complicated part for the UI? The x position of the drop determines the subtask level from one of a list of allowed levels. This list is calculated via a function of the mouse y position during the drag. Allowed levels start from the level of the task below the drop location and count up until they end at to the level task above it + 1. That's how the UI of another app that I use called ClickUp behaves although I've not seen its source code. It's true that some users might find this to be too complicated for their liking, so perhaps it could be configured in a setting called "Multilevel Subtasks" on/off. That way everyone wins. Personally I don't use Jira so if the Jira integration isn't compatible with this feature yet, the user could just be notified of this when they change the setting and the Jira integration could be temporarily disabled. If someone can provide guidance to which file in the source could contain these edits, I'd be happy to possibly take a shot at it in a fork and make a PR later if I succeed and if that's ok with @johannesjo. Or if @johannesjo wants to do it maybe a few of us would be open to considering sponsoring his time for the feature if he would be open to that.

[johannesjo]

Is drag and drop the complicated part for the UI

No the complicated part is the displaying the controls as needed on many variants of different available spaces :)

On the logic level this is a huge change too, since parents and sub tasks are connected on some levels. There would need to be a propagation logic.

What I'd rather implement is improving adding lists on the task side panel level (currently possible via the task notes). I think this might be a better solution. There it should also be no problem to add infinite levels of nesting there.

[Korne127]

What I'd rather implement is improving adding lists on the task side panel level (currently possible via the task notes). I think this might be a better solution. There it should also be no problem to add infinite levels of nesting there.

Hey, I can just say that from a user perspective, while this is an improvement, this is no real replacement, and sadly no "better" solution.

Super Productivity looks really promising and is a great app, but the lack of nested tasks sadly is a dealbreaker for me. Personally, many if not most of my tasks are nested. And I don't mean lists. I would use (nested) lists for categorising stuff (e.g. Programming -> Private Projects; Open Source Contributions // University work -> the individual subjects // Everyday tasks // etc.). But a big share (at least a third) of my tasks are nested; from a specific programming project over buying groceries to answering to messages. This means I'd have literal hundreds of lists, which is just no working solution.

[Korne127]

Random thought, but maybe it would make sense to make a bounty for this? There are definitely quite some people who need this feature, and would be willing to support devs for making it real. Maybe in combination this can be an incentive to try and make this real.

[johannesjo]

Random thought, but maybe it would make sense to make a bounty for this? There are definitely quite some people who need this feature, and would be willing to support devs for making it real. Maybe in combination this can be an incentive to try and make this real.

Sure we can try this! I am not fundamentally against the feature (though I think productivity wise it might not be a good idea to nest your tasks this way).

[RokeJulianLockhart]

#2657 (comment)

@johannesjo, I merely want to ensure that relationships are preserved. Whether they're indicated in a purely hierarchical tree like this issue proposes, or something more versatile like tasks/tasks#1868 (comment), is inconsequential as long as the original task data is preserved, and I can still see the relationships somehow.

[Korne127]

though I think productivity wise it might not be a good idea to nest your tasks this way

@johannesjo I currently use TickTick (which supports nesting tasks up to five levels) and for me, keeping track of all my To-Dos and managing them would be impossible without this. (I'd just have a huge pile of todos and get lost in it while a tree structure allows me to save relations.)
I think this is just something personal: There may be people for which this doesn't work, but I'm sure that there are also many people which need this to be productive.

But I can imagine that there are (both frontend and backend-wise) some challenges to do this.
I think TickTick actually does this pretty decently, especially frontend-wise. It shows how you can make a good system to Drag tasks around, etc. while still having more complex task hierarchies.
About the space problem: I think it's actually pretty rare that you have a task with more than 5 levels open. A solution that's pretty easy to implement and works pretty well would be that starting at a specific amount of levels that are open, a horizontal scroll bar is introduced for the respective top level task, so that you can scroll to the right for the nested subtasks. This would provide a good solution to the (very rare) edge case of having many tasks open without creating any disadvantage for the average usage.

The one thing that would be important imo when introducing a task hierarchy would be an option to enable / disable task breakup (meaning that when disabled, you see the task hierarchies, but when enabled, you see all sub-tasks as (closed) top-level-tasks as well). This is necessary if you add due dates to subtasks and want to sort all tasks by their due dates (which is a pretty common behaviour).

[dwiehoff]

@Korne127 Are you saying that the many sub-levels help you to organize and structure your tasks? Would you have a more extensive example of what this would look like in practice? Maybe there are alternative ways to achieve the same result.

[BeatLink]

A lot of productivity tools recommend breaking large projects down into more tangible actions. nested tasks are vital to this. Without nesting, your tasks may have a big picture overview but be vague and unactionable and lacking details. Or your tasks may be specific and actionable but lacking the context of the big picture

Say for example you have a task to tidy your apartment. With a nested structure it would look like this

• Tidy Apartment
  • Tidy Office Space
    • Clear Desk
      • File all paperwork

And each of those 4 levels would have other sibling tasks.

If you only tracked the 4th level detailed tasks, your workday would become chaotic and disorganized, jumping from specific task to specific task while not having a clear picture in mind as to what each task is leading up to and when a project can be actually considered done.

If you only tracked the top level tasks, your workday would still be chaotic. You would know what to do in the large scheme of things but not the specific actions to get to those goals. And even if you did know the specific actions, you would have to think and decide what those actions are every time you start and stop working on that project.