| Welcome! | English (US) ![]() |
| Welcome! | English (US) ![]() |
Has anyone asked for this yet? It would be incredibly helpful if I could check off the items in a single task one by one as subtasks, rather than creating separate tasks for each. I know this is approaching a "project management" status, but would be helpful in the context of "remembering the milk", too.
Posted at 1:53pm on October 19, 2005
+1
Posted at 6:27pm on October 29, 2005
says:Without wishing to complicate RTM, this would be great.
Posted at 6:08am on October 30, 2005
I want this too.
Posted at 6:44pm on November 2, 2005
says:This is a good idea that I would want also, but it's important to me that the simplicity of the interface be maintained.
Posted at 10:46pm on November 2, 2005
+1
This would be great for me. I have many projects that can be broken down into tasks, subtasks, etc. Currently I can work with this by creating extra lists for subtasks, but it's a clunky work-around.
Posted at 4:22am on November 3, 2005
Subtasks that can be collapsed.
Posted at 6:18am on November 9, 2005
I have been listing sub-tasks as notes attached to the main task. Works for me. You could also create a separate tab for large multi-step projects and list sub-tasks as individual task on that tab.
Collapsable sub-tasks sounds nice in theory, but I love the simplicity of this interface and I'd hate to see it become cluttered and cumbersome.
Posted at 11:25pm on November 9, 2005
The reason that we haven't done subtasks is that it would be extremely difficult to do without complicating the interface (and we've already packed a fair few features into this interface :)
Not to say that we would never do it in the future -- but it would require some serious thought to ensure the simplicity of Remember The Milk was maintained.
Posted at 1:23am on November 10, 2005
Well, indeed that's the dilemna. Everyone around here seems to think you've made pretty good decisions about the interface, and certainly there are some pretty poor interfaces on 'competing' tools. (Though to be fair, people who don't like it might not stick around long enough to post in the forums!)
So might it be possible to hide away something in the settings to "turn on" a more advanced interface for those that decide they want it? Maybe once this and some other wishlist items have appeared it might be easier to see how to add some more advanced things in this way.
Posted at 9:14pm on November 12, 2005
One simple way to implement this could be just indented lists in the current interface.
* TasK (V) <-- this will fold or unfold the subtask list
o Subtask1
o Subtask 2
You'll need to have a little more info in the right pane when a subtask is showing and some keyboard shortcuts. Some constraints/more options on when a task can be marked as completed (depending on subtasks).
I'd like this too, obviously.
Posted at 12:46am on November 14, 2005
I vote for subtasks too... this is the first limitation I came up against.
Posted at 12:53am on November 18, 2005
Yep need nested tasks
Posted at 1:52am on January 15, 2006
I would really like this feature as well. I have 4 lines worth of tabs of lists which means that I have less and less space to list the actual tasks. Some level of heirarchy would make all the difference to me.
Posted at 1:31pm on January 24, 2006
Please....subtasks. That would make RTM works with my life. Please.
Posted at 6:59pm on January 27, 2006
As we've now provided several ways to organize tasks (tags, lists, and Smart Lists), we have no plans to introduce subtasks.
A workaround for subtasks might be to use lists and tags -- for example, I have a list named 'Shopping', and within that list I've tagged tasks with 'supermarket', 'mall', etc. I can then view tasks tagged with 'supermarket' in my 'Shopping' list, which helps to break down the list.
Hope this helps!
Posted at 4:53am on January 28, 2006
I've been using RTM for a few weeks. I was about to suggest the "subtask" feature before I did a search to find this thread.
I support nested tasks or subtasks.
I'm wanting something like:
# buy concert tickets
# website redesign
# covert database to xml
# update css
# find new hosting provider
# install wordpress
# mail photos to Erin
I feel that listing the "subtasks" as individual tasks would clutter up my RTM main tasks page, so I don't want to add them.
It appears that RTM isn't really suited for project management. However, I must say, that in my search for decent project management software, I haven't found any that I want to use. I got excited when I first found RTM. I think it's a great tool for personal use. However, I'm hoping it will expand its features to better support project management.
Thanks.
Posted at 8:25pm on February 6, 2006
Sorry, I had started a new subtask thread before finding this one.
I've just started using RTM and will check out the lists and tags features.
Thanks!!!
Posted at 4:19pm on February 15, 2006
It will be greate to have the subtasks feature.
Posted at 2:15am on February 24, 2006
I think RTM works great for what it is -- personal task management. I don't think adding subtasks is a good idea for that very same reason. If you want to manage a work-related project, I would suggest using an actual project management application. Basecamp is what I use, and it works very well in that respect.
Posted at 1:19am on February 27, 2006
says:I can understand why the developers don't wish to implement subtasks.
The 'solution' of using lists/tags is a good one in general, though there is a possible problem of having too many lists/tags?
Has anyone tried this as a simple project management online tool?
http://www.ioutliner.com/
Hope it's ok to post the link
It is fairly basic, but has a neat way of adding/moving task. Certainly not a replacement for RTM, but maybe something also to use
But I'm going to pursue using lists/tags for now and see how it goes
Posted at 1:30pm on March 1, 2006
I initially wanted subtasks as well and suggested this Emily. I got the reply as above from her and I have to say now, that I totally agree with her.
Adding subtasks would complicate the view of the site - which is the strong point of RtM and it would trigger a whole lot of other requirements such as interdependencies between subtasks and before you know it, this is a project management tool and not an action list tool.
I suggest reading the "Getting Things Done" book by David Allen and understand why simple lists (Actions, Projects, WaitingFor, Someday/Maybe) sorted by e.g. @Office, @ Home, @Car, @Online etc. rules. Being able to add multiple tags even improves upon the GTD approach! You will not be able to do this by using a hierarchy of tasks.
Posted at 9:54pm on March 19, 2006
+1
Subtasks will be a challenge to implement, but would be great. To anyone who said it will be simple....it seems that way till you think about the details.
Nonetheless it would be a huge feature for a lot of people.
Also agree with the above comment about turning it on/off to keep the interface simple.
Reading the above -> I wonder if a label could be a task which can't be "completed" till all tasks with that label are. You could sort of nest these, but that might be too wierd.
Posted at 11:49pm on July 2, 2006
I wouldn't want this because of the aforementioned cluttering of the interface.
Perhaps you could just create a list to represent your main task, and then the subtasks go in that list. Then once you are done with the subtasks and the main task, just archive the list.
Or you could organize a pseudo hierarcy with tags and smart lists.
RTM is functional just enough to allow for these things to be artificially implemented by each user than to force every user to deal with it.
Posted at 1:25pm on July 6, 2006
If it were possible to turn this feature on/off then I think it would be incredibly helpful for those that would use it. And not affect the others.
I for one, would like to see subtasks and a way of ordering them. But recognize that it is no easy feat to implement and causes future enhancement delays as the level of complexity increases.
Posted at 2:31pm on July 6, 2006
+1 indented subtasks, simply set from the right hand toolbox via a "parent task" dropdown of tasks in the same list. or perhaps linked tasks? Realise the other ways of tagging tasks, I will try that and for now I will keep notes against each task. Is there a feature request to show the notes under each task (the first 15-20 words or so) with a [+] expand button to show the full notes. This would allow ppl to quickly browse their notes for a task and for me would negate the need for sub-tasks. Cheers, love the simple-ness of the app interface.
Posted at 11:03am on January 14, 2008
I would really like sub tasks as well. I found RTM after looking at Things (http://www.culturedcode.com/things/). Things is the perfect solution for what I want except it's not online.
Posted at 1:09am on January 20, 2008
says:Ohhhh yes ! I vote for this. It would be easier to manage tasks by the GTD principles.
:-)
Posted at 7:04pm on March 25, 2008
I use Remember the milk to help me to control my projects. I know I need a tool for project management, but, if RTM could implement subtasks it wolud be very helpful for me.
Posted at 6:57pm on March 26, 2008
I have to agree that this is by far the #1 issue that I would love.
Posted at 4:37pm on March 29, 2008
I also think that subtasks feature would make an extra positive difference pro RTM. And there is no conflict between GTD system and subtasks! Could subtasks feature could maybe be included as a pro user option. I think it would be a very useful implementation for RTM, specially if not the only possibility regarding the interface, but as an extra and valuable feature.
Posted at 6:00pm on March 29, 2008
says:Yes, it is what I mainly miss. It would be even nicer if they are automatically dependent tasks - In other words, they show on my list of things to do next only after the prior item in the list is completed - and all default to the do date of the "master" item.
Posted at 9:45pm on March 30, 2008
:-/
I just got 'April Fooled' by the subtasks thing - you almost had my $25. Not cool. Or particularly funny.
Anyway +1 fwiw
Posted at 5:39pm on April 1, 2008
says:Well, I think that was rather funny.
Please observe that the poster was Emely, not Emily.
Posted at 6:47am on April 2, 2008
As a web app programmer, I understand the complication that sub-tasks could add to the UI... but... perhaps there could be categorized lists or 'sub-lists' instead. That way, all that needs to be accounted for is a hierarchical relationship between the lists and not really the tasks.
For example: Most of my tasks are broken down by "Work" and "Personal"... but under work I might have a few lists... such as "Admin Tasks", "Project 1", "Project 2" ... or for "Personal" I might have "Outdoor work" to remind me of yearly maintenance around the house or "Cleaning" or "Workout" ...
I realize that there is tagging, and being new to RTM I have to play with this to see if it can help me w/ organization, but categorization of my lists so that my "Tasks" view doesn't have a million lists in it seems like it would be helpful.
Posted at 1:02pm on April 4, 2008
says:One way to get some subtask functionality could be tweaking the excellent Grease Monkey script (Firefox/Opera only) by masnare. See more in www.rememberthemilk.com/forums/tips/2943/
One way to implement subtasks:
Posted at 2:05pm on April 15, 2008
mash it up! if rtm doesnt use sub tasks then make use of the url link you can add onto a task to link through to sproutliner or ioutliner, this is my approach i like the siplicity of rtm and it works for me 99% of the time for bigger projects i link across. it would be great to see this embedded into rtm as standard but can understand why they dont
Posted at 8:03am on May 2, 2008
Yes!
Sub-tasks are the one feature I miss in all the GTD tools i've tried. I don't want the bloat of MS Project, but my goals do require more than a single action to complete.
I'll use the list/tag/label workaround suggested above until then.
Posted at 1:28am on May 19, 2008
I've just signed up for RTM and within 5 minutes I was looking for a sub-task option. All I need is to be able to add a few check boxes to a task, each with my own label. All of the 'clutter' (tags, location, reminders etc.) could remain at the task level. Using notes or tags is messy and fiddly and actually detracts from the simplicity of the tool.
Posted at 8:15am on May 19, 2008
I like how these guys do subtasks...
http://todoist.com/
Very easy to use and very flexible and able to do as many subtasks as required (ie. sub sub sub sub task).
I don't understand why rtm doesn't have subtasks. It was also the first thing I looked for when I signed up. Its also the only reason why I don't use rtm much, because theres no subtasks.
Posted at 3:25pm on May 19, 2008
I've moved to todoist.com, they actually seem to rate functionality.
Posted at 7:39am on May 27, 2008
says:Perhaps the word of a PRO user is listened to more carefully:
I also would love to have collapsible, recursive sub-tasks. Should not be complicated to implement (parent references in the data structure) nor to present to the user (tree widgets are used all over and are familiar to most users).
It should be implemented in a way that if a user does not create any sub-tasks, the UI will not change.
Please do not make me regret paying the subscription fee.
Posted at 11:39am on June 20, 2008
says:This is fairly simple to do with the existing structure. I do it for work:
Create a task for your first sub-task. For example:
Rewrite interface logic to robot
Tag this with your main project name. I use a predecessor character for organization.
+Packaging_Rewrite, @work, na
This indicates that it is part of the packaging system rewrite project, it is performed at work, and it is a next action.
Add the rest of your subtasks in the same way.
Finally, do a search for +Packaging_Rewrite. Save this as a smart list called Packaging Rewrite. The tab is your project, inside of that are your subtasks.
You can go a step further. Create a task called Packaging_Rewrite. Tag it as:
*Projects, +Packaging_Rewrite
Again, search for tag:*Projects. Smart list it. Now you have a list of your projects, and each project has a list of sub tasks.
Is the interface layout exactly what you want? Probably not. Does it accomplish the same thing that you are looking for? YMMV, but it works quite effectively for me!
Much of this concept was inspired / directly stolen from this thread:
http://www.rememberthemilk.com/forums/tips/2943/
--Tutunkommon
Posted at 5:30pm on June 23, 2008
says:Quite nice workaround... but it still remains a workaround.
I work for a software developing company and it never seize to amaze me the sometimes unexpected strong and sudden explicit conviction of the developers about to specifically do or specifically don't do things (change requests) in a certain way, in spite that there are dozens (in RTM-case probably: thousands) users and even co-workers and bosses literary screaming for certain changes in the software.
Mostly after months of hours and hours of endless debates and mind wrestling, begging, teasing, bargaining and threatening they suddenly 'flip a switch' and built it in a few hours and present it as if it was self-evident.
(And, my dear RTM-developers, of course: receive the world fame and glory during the standing ovation of masses of happily surprised customers who are all eagerly empty their wallets for you, and you will all get promoted to your dream job you have worked your whole life for!)
Posted at 9:02pm on June 30, 2008
This discussion shows that there is a real need (should I friendly say a lack ? ) for a "project" notion (or level) in RTM.
of course lists can be used for that (as suggested by Doug in RTM blog) but then lists can not at the same time gather tasks of the same field (because we would like thos lists to list projects too among tasks).
some kind of hierarchy is needed : a project level
At the same time I understand the motivation behing RTM people (Emily) that one of the magic of RTM is making a boring subject (to do lists) an enjoyable application we go to with pleasure.
For that simplicity, in the line of the original concept has to be maintained.
I think this is possible, the two requirement (project and simplicity) are conciiable, RTM people should think on how to do it simple and well.
but I think neglecting any of the two requirement would be an error
1) neglecting simplicity and attractivity of RTM would end in RTM not staying RTM anymore and people could walk awy from it
2) neglecting the need for a project notion, would be neglecting a real and durable need in to do list and GTD and sooner or later people needing it would leave, reluctantly but still leave for applications dealing with the project level. That would be too a bad news for RTM people.
so it is up to RTM people to find the appropriate means to deal with a project level (or hierarchy) in RTM, but in everybody's interest we'd like them to find one.
I'm not sure the best way is by adding sub-tasks, it would indeed transform RTM in something more complicated.
why not use projects that could includes tasks and could be listed in lists (?).
Any way I think the idea for subtask, like the idea of gathering lists in tabs or any other way of list gathering stem from the same reason : "finding an appropriate way to deal with projects".
so RTM people we are with you, find the solution, we can help you choosing or selecting among alternatives
and may the milk be with you
Posted at 1:45am on July 2, 2008
- 1
The existing smart lists are much more elegant solution.
Posted at 3:32pm on July 2, 2008
this is a way of doing it but here are my arguments to explain why it does not meet the objective :
- you do not have project attributes (next action, etc.)
- you rely only on tags that you manually enter :
let us say a tag for the project name, a tag for next action etc.
the thing is that it is far too manual, the risk is that you omit one of your tags or your make a typo error and the system is not consistent.
and if it sufficed then why would RTM have lists at all ?, it could also be done with tags and smart list
and going further on that logic why not do everything with text files etc.
like Emily said one key advantage of RTM is that simplicity,
you have tasks and lists as elements on which you can develop smart lists.
I think there is a need for a (simple) project element, with some relevant attributes that could then take advantage too of smart lists for further people personnal elaboration.
but to me smart list are not appropriate to substitute for a project level, that in my view :
- has to be able to gather tasks
- has to be able to be listed in lists
(and has to have some relevant project attributes)
Posted at 7:32am on July 3, 2008
I would really like real sub-tasks :)
Posted at 12:44pm on July 3, 2008
i want subtasks
Posted at 2:16pm on July 3, 2008
sub tasks do not really make sense because what is a task with sub tasks ?
- a project
a project is any task that require more than 1 task to be completed
it perfectly makes sense that a project contains tasks and project
example :
I have the project "sell my house"
it could be in the list : "housing" in which you would find the other project : "find my next house"
back to project "sell my house", it could contains projects such as :
"assess worth of my house", "refresh my house for better looking and selling","find the best and least commissioned way to sell it"
in the project "assess worth of my house" you find the following tasks :
-"identify 3 housing assessing expert"
-"contact housing assessing expert 1 for an appointment"
-"contact housing assessing expert 2 for an appointment"
-"contact housing assessing expert 3 for an appointment"
-"determine the price of the house synthesizing the 3 experts results"
Now remarks :
1) imagine the mess if each project is a list mixed with original lists like "housing"
=> projects should not be implemented by lists if lists keep their current signification
=> you have to have an "atomic" level of to-do action, ie an elementary action that need not be further subdivided
in my opinion this is RTM tasks so subtasks are not necessary if
project level exist.
Many GTD people consider that any to-do action that require more than 1 elementary actions is a project.
Posted at 3:58pm on July 4, 2008
I agree that sub tasks would be nice. I am using lists now to contain big projects but sometimes I have a simple thing (a little project) that has some components (sub tasks).
Posted at 4:50pm on July 9, 2008
I would also like to have subtasks.
Posted at 1:23pm on July 22, 2008
and another +1 for collapsing subtasks
Posted at 8:08am on July 30, 2008
+1 for sub-tasks/dependent tasks...
RTM is very flexible and some people have found some ingenious ways of using its current interface in many ways BUT all of the ingenious implementations I've seen on these forums for managing nested tasks/ sub-tasks/dependent tasks are NOT simple or elegant, but turn using RTM into something arcane, complicated and non-intuative which is not what it should be.
Anyone who is trying to make a list of tasks will find that some depend on others or one task is better written as sub-tasks (and I dont want to have 15 projects!) This is the one thing that makes rtm frustrating.
Sometimes adding functionality complicates things, sometimes it can simplify things...
Maybe there is a way and preserve rtm's simplicity, elegance, and flexibility?
Posted at 12:51am on July 31, 2008
says:I don't like hearing that adding features has to complicate things.
Good award winning developers (hint...hint...) find ingenious ways of implementing obviously high demand features without complicating things at the same time. Sub tasks does NOT have to complicate things if implemented correctly. Folks that don't want to use them don't have to but folks who do, can. toodledo (horrible interface btw...) has done this by turning off subtasks by default but letting the user who wants that functionality to turn it on in their individual preferences. Ingenious... no?
Implement sub tasks yesteday please.
:)
Posted at 2:14am on July 31, 2008
says:Whew, I just read this entire thread and have to agree that subtasks are a must. I considered upgrading to pro, but as I was digging through the FAQ and such I found that subtasks are not implemented and, at least as of January 2006, is not on RTM's development radar.
This is lamentable as I love the mobile and sync integration, but I'm going to continue shopping other solutions as the lack of subtasks is a deal breaker for me.
I perfectly understand the nested / multi tagging solutions, but they are a band aid and end up making it a lot more work than it should be. I'd be willing to bet that if subtasks were implemented, most if not all of these nested tag hacks would vanish into the ether... for South Park fans, picture Cartman's hand waving around after J-Lo jumps off the bridge in "Fat Butt and Pancake Head".
I like tacos y burritos
Posted at 2:45am on July 31, 2008
I just signed up for RTM. I am looking for something to manage personal tasks such as finance, kids, household, etc. Sub tasks are so logical. For example I need to get the kids registered for school but need to get a sports physical for one and eye tests for all of them before that. I also am planning on staining the deck but I need to pressure wash it, pick up the stain and supplies. These type of lists really lend themselves to sub tasks.
Posted at 2:51am on July 31, 2008
This seems ridiculous.... For as many users that have requested this and it not be implemented. It is an embarrassment....
Posted at 11:41pm on July 31, 2008
says:Please count me in on the list for the FEATURE REQUEST of SUBTASKS.
I like everything that RTM is offering, but the lack of SUBTASKS is pushing me towards other options.
SUBTASKS are much easier to link to the original task/project then creating a TAG. When you create the TAG you are doubling the effort and often times if you don't remember what TAG you assigned to the initial project you end up creating a new one.
It is much easier to scan your todo lists, locate the TOP level task/project and add a SUBTASK to this initial entry.
Please ADD this feature ASAP as it is something I would most definitely pay for!
Posted at 9:49pm on August 4, 2008
-1
I really don't want subtasks. I think it's easy to do this by defining a project with a certain tag (.project or whatever) and then making a smart list with the "subtasks" required. I think this will really take away from the lightweight, clean look of this application.
@phugel
Yes, same here. When I create a task, it's the ultimate goal. Then I keep track of progress and what else needs to be done in the notes section. It's great to have all information regarding a task in one place -- especially if I need to reference back after the task is completed. I have a running log of everything that took place to get that task finished.
Posted at 4:03pm on August 5, 2008
says:The other way to do it would be to add a note. When all things in the note are done, the task is completed. Use of tags gets me most places. I'd prefer not to overcomplcate the interface and would like an even simpler one.
Posted at 5:15pm on August 5, 2008
@ianm17
Right on.
Posted at 7:29pm on August 5, 2008
put me on the list for subtasks and ill upgrade to pro in a heartbeat....
sad that this has been requested almost 3 years ago and still has not been implemented. I don't know what the big deal is about implementing this feature. If your subscriber base wants it and there is a potential to bring in revenue for the feature I don't see a reason not to implement it.
Posted at 3:10pm on August 6, 2008
The issue: "The reason that we haven't done subtasks is that it would be extremely difficult to do without complicating the interface (and we've already packed a fair few features into this interface :) Not to say that we would never do it in the future -- but it would require some serious thought to ensure the simplicity of Remember The Milk was maintained."
I don't know what's going on in the RTM staff meetings, but I'm sure they are aware there are many who want subtasks. Isn't it ultimately their prerogative what they do with that information?
Lastly, I'm really confused as to why so many people push so hard for this subtasks feature. Maybe I can't picture what's being requested, but I've always thought the best thing about RTM is how flexible it is; because of this you can create subtasks so many different ways. Maybe the tag system is a little different from other task management tools (I'm not sure), but there are lots of websites and people who've posted in these forums with great ideas on how to keep tasks (including sub tasks) organized.
Posted at 3:45pm on August 6, 2008
Hi!
I would love collapsible, dependent sub-tasks (and sub-projects).
I am currently using the free RTM, but would pay to upgrade to PRO if this were a feature.
I would also feel that I had found nirvana, organization-wise.
As it is, I already feel I'm close to Shangri-La...
Thanks for the work you're doing!
Posted at 8:17pm on August 6, 2008
I would still love to see Subtasks
Here's a greasemonkey script that impliments them (but you have to be mindful of your tags).
http://userscripts.org/scripts/show/27614
As you can see from the screenshot at the bottom, it doesn't seem complicate the UI.
Posted at 10:03pm on August 14, 2008
says:I'll throw in a +1, though the notes interface allows users to list their subtasks there as well (not as ideal because you can't click "complete" but still a place to group subtasks under a main task). So, if notes usability was improved as noted in the other thread, the need for subtasks might dissipate.
Posted at 2:36pm on August 17, 2008
I really want subtasks too - I would probably even be willing to pay for pro if it had subtasks.
I don't see why this would make anything more complicated - just have some indented subtasks that could collapse under a main task. They don't even have to have tags if that makes it more complicated. I don't think subtasks would go against the basic philosophy of RTM or turn it into some kind of complicated "project management" tool.
It's much messier and more complicated to make a new tab for each task that has subtasks, or use tags to identify some tasks as subtasks of another task, or even to list subtasks in the notes.
I think that categories (i.e. tabs/lists), main tasks, and subtasks is the way most people organize - obviously by the comments lots of people want them. So why is RTM so opposed to subtasks?
Posted at 7:04pm on August 25, 2008
says:I'd pay for pro if it had subtasks. Perhaps you can offer them as a setting on each list, so that they don't have to be turned on and complicate the interface for users who won't enjoy them.
But for my schedule, anything that would manage my todos must have hierarchy options.
Posted at 3:12am on September 1, 2008
+1
Posted at 8:48pm on September 2, 2008
The Greasemonkey Script "RTM Projects" is the only reason I am still using RTM without Subtask support and shows just how clean and simple it could look.
Does anyone else feel like they're not trusted to know what they want?
Posted at 2:36pm on September 9, 2008
+1
I too definitely would appreciate having collapsible subtasks to organize which tasks need to be performed in order to complete other tasks. Sure, there are "manual" ways to emulate subtasks, but surely that just demonstrates the demand for the real thing?
Posted at 5:25pm on September 9, 2008
this has to be #1 most requested.
Developers, I know it's your product... but #users vs #devs on this issue surely has to make you wonder if this feature will increase your user-base if not enhance the product?
If every single RoR user requested one feature that went against MVC, surely the higher-ups wouldn't say "No, use tags"?
I stopped using RTM because of this issue, and am only back to see if it's been implemented yet...
Posted at 6:27pm on September 10, 2008
says:Hi everybody,
I agree with RTM designers. Subtasks are a mess to develop. As the number of RTM users is growing (800.000), a subtask feature would complicate the application and turn the interface sluggish.
Look at the BIG actors, like Microsoft Live Calendar new tasks. They don't even have contexts!
There are many ways to implement "subtasks" in your RTM:
If your task contains a lot of subtasks (more then three), don't hesitate to create a list, even with a prefix to link it to its main list (kids, tax, etc.).
If your task does not deserve such a treatment, use the notes, one per subtask. Select your main task, then press Y to create a note, one per subtask. When your subtask is done, you can insert an "ok" or "done" in it.
The Y shortcut is very powerfull: it displays notes and opens a blank field to enter your next subtask.
Use also the "hasNotes:true" smart list to display your "big" tasks and decide if they have to become lists.
Cheers from Paris,
David
Posted at 6:09pm on September 20, 2008