Personally, I'd find that a bit too much. I'd prefer to have a large number of small tasks around. Create a new list if you want the tasks grouped together. If the subtasks are really small, you could group them into reasonable-sized chunks to knock off. Perhaps "Call 5 clients" with the clients in the notes.

Perhaps it might be more useful to have tasks like "do one day's work on project X", or "write five pages of manual Y". You can use recurrence to keep the task on the list.

My request was not for a better way to group tasks, but for a way to track which ones are in progress without having to rename the task. (Currently, I add a "+" in front of tasks that have been started. It works but I figure it never hurts to ask for a new feature!)

FWIW, I don't have a large number of "projects" that I'm handling in a single task. More often the things that carry over for me are tasks like "Set up new computer lab" or "Upgrade OS on x computer".

I guess it is like a dependency tasks, but RTM developers has no plans for that.

How about naming your task "Set up a new computer lab (35%)" or "Upgrade OS on x computer (###-----)" A touch clunky, but it's so fast to edit the task name that it shouldn't be much trickier than if the task had the indicator built in.

That's pretty much what I've been doing. It works but, like you say, a touch clunky. It's not hard to edit the name to indicate progress, but the other software I was using (Now Software's Now Up-To-Date) would put a "-" in the status box and change the status box color to yellow. That way, it was very easy to do a visual scan of in-progress items without having to read each title.

I'm making RTM work and it's not a deal breaker by any means. I just thought I'd throw out another suggestion.