_____________________________________________________________________________
Many tasks can belong to different parents naturally.
I will use this feature all the time.
I walk the neighbor's dog (task) in order to help the neighbor, but also in order to consider to adopt a dog, also in order to make my weekly sport routine.
I organize my desk (task) inorder to find my car wash business card (task / note) so I can wash my car (depented task) inorder to publish a good picture of the car (parent task) inorder to sell the car (project). so far so good. I also organize my desk because I prepare the office for meeting with the insurence guy (parent task, note: good impression is important) inorder to insure the company's imployees and get the best deal (project). I also organize my desk in order to clear my head in order to be more productive (goal / folder). I will need to do it with the Secretary becuse she knows best what goes where (context).
so it's gonna look like that:
- check out the craigslist website
- publish a good picture of the car (sinquential parent)
- find my car wash beisnes card (parent task)
- organize my desk (note: maybe the car wash business card is there) (@Secretary)
- organize my home desk (maybe the card is there)
- take a picture of the car
- upload the car picture to craigslist
- ensure the company's imployees and get the best deal (project)
- prepare the office for meeting with the ensurence guy (parent task, note: good impression is important)
- organize my desk (note: maybe the car wash business card is there) (@Secretary)
- be more productive (folder/goal, note: being more productive will allow me to clear my head and will bring me more success in all areas of life)
- organize my desk (note: maybe the car wash business card is there) (@Secretary)
btw, maybe I want to go to that specific car wash because of different reasons which can be represent by the tree as multiple parent tasks as well.
I can't represent these connections with dependencies alone. organize my desk is an unbreakable part of more than one parent task or project. sure, I can workaround it, put this task under "organization" folder and make dependencies to the other tasks, but it's not the natural way. the relationship between the tasks, if it's any dependencies - it's FF dependencies and not FS dependencies.
contexts are not part of the tasks tree, are not hierarchical and cannot have their own fields like completion box, dates etc..
still, workaround is possible if there is only one case. Dependencies, links, contexts, views, duplicates, subtasks of subtasks., notes... etc ... Workaround around a 100 cases or more is not reasonable.
I want to see everything that need to be in hierarchical tree - in hierarchical tree.
It won't be to cluttered
The tree can only become more clear as each task can belong to more than one parent
This feature will allow me to review my work (task, projects, goals etc) in a much more effective way and to execute my actions based on ten times more effective natural priority system. my life will be organized.
it comes handy even more when one defines a lot of "general goals" like: be a good grandson, be healthy, always learn more...
"walk to the library with your grandmother" can fit to each goal as a sub task. Completing this task will fill more percentages in the progress bars of the goals (if they been set as projects) for better trucking. Goals and projects can be subtasks of multiple parents as well. folders can belong to multiple folder parents. a lot of projects and group of tasks can belong to multiple areas of life as well.
Me personally - I will use this feature a lot. in a lot of ways.
I will group all tasks from different roots that share the same finish to start dependency chain (with the already exist dependency feature in MLO) under the same parent task.
I will attach all my contexts to folders and will organize them in a tree, then will include tasks on those context folders so it will inherit the same context.
It will also allow me to add more contexts and use them as tags as well, without overwhelming.
how should this feature work?
general
- in the settings there will be an option to open the app for the cloning feature, by ticking the option on and off. this will allow poeple to be aware of the feature and use it smartly.
- by ticking the "on" option, each user will be able to include each task in any other root without any limitation, (including top root).
- except one limitation: a task cannot belong to another task from the exact same root, example: if task a is the parent and task b is the sub task and task c is the sub sub task - task a or task b cannot be included as subtasks of task c, as a task cannot be a parent and a child of a another task in the same time
- The option to have a "natural" parent will remain. each task can have an "original" parent and "tags" parents. if one goes to settings and turn the clone option off - he can see the typical hierarchy again, without no "clone tasks". personally I will probably not use this option, but it's good to have "back up" plan for those people who may need it
- basically each task can belong to multiple parents. clone / link, the idea is the same - it's the same task! if I change the task fields - the "cloned" tasks are changed as well. if I add or delete subtasks of the tasks - so are the subtasks of "cloned" tasks, because it's the same task only belong to multiple parents. all the "cloned" tasks even share the same creation date.
the way we clone tasks
- on both mobile and desktop: the "move task" option will be still exist aside with the new option "include task" (just like we can do now with dependencies pop up, just tick as many tasks as we want in one time)
- on desktop: task can be included as a sub task of other task with drag and drop with right click on the mouse will open a pop up with the possibilities: link / dependency / clone (just like now but with clone possibility as well)
- on mobile: the task long-pressing is loading a small tool bar that from there we can copy/paste. 2 new options will set - "clone" and "paste clone"
search&path
- If I search a task which belong to multiple parents - I will get only one result - as it's not really a clone, it's the same task! ( its parents function as tags... )
- path of the "cloned" task - . the path per task (which we can see under the tool bar on the windows version and in the task description on the mobile version) can show only the "original" path (option #1)
- even better than that (or on top of that) will be to be able to view a list of the direct parents of the task, just like we can view a list of the assigned contexts for each task (option #2)
- if it's possible to implement it - I would like to suggest to be able to view the whole path from the task description or from under the tool bar - instead of showing the "original" path, one will be able to view a list of the direct parents of the task. another click and a new window will be opened where the whole path is shown, starting with the direct parents on the top of the list and organized in opposite hierarchical tree, this tree can be exist for a read-only mode for reference of the whole task path. (option #3)
task inherit behavior
- dates - Dates of the cloned task will remain the same dates as before and will not inherit their parents as each parent can have different set of dates or another option will be to inherit the earliest start date and the latest due date
- context - the user can decide if inheriting the new contexts or ignoring them. just like now. no change here
- computed score - the computed score of the cloned task can inherit the score of the "original" parent or another option will be to inherit the highest computed score and ignore the "lower computed score" parents
- Hidden todo - if one of the cloned tasks belongs to a hidden branch - then the task will be hidden everywhere or a popup window will appear and let us decide what to do with the cloned task - *leave it hidden or *stay visible even inside the hidden branch.
- Project status - if one parent has 'complete' status, and the other parent has 'in progress' status - the task will inherit the 'in progress' status
- visibility in the todo list - if a task belong to one parent that is "locked" (completed or has uncompleted dependencies) and to a second parent that is "not locked" - then the task will show up in the todo list as it is an active action
Project completion bar&time required
Projects will be 'fed' from their "cloned" subtasks as the cloned subtasks are real subtasks!
I hope I made my point clear enough as I'm writing this from my tablet on the go and english is not my mother tongue.
all the best
John