Forums / Tips & Tricks

graham.reeds

That's what I do for the task hierarchies.

It would be nice to have date arithmetic so you didn't need to go through each one changing all the due dates when one runs over due.

G.

Posted 5 years ago

rajjan

[Slightly off-topic] Regarding due dates: Why add due dates to tasks that don't really have a due date? Most of my tasks are ASAP, that doesn't mean they have due date "today". If you can change the due date at will, was it really a due date? Due date "never" is OK ;-)

Posted 5 years ago

Yep, following GTD, I only use due dates on calendared items and on Next Actions that have a deadline. Others stay never.

Posted 5 years ago

bruce.reynolds

This looks like a WBS, which goes way beyond the scope of industries and people who have no idea of what WBSs stand for. WBS is an acronym that stands for Work Breakdown Structure.

By the way, if you can pull off implementing a live WBS capability that can be accessed successfully by various interested parties online, you would have a whole new set of customers that would be willing to pay big bucks for this capabiltiy.

Posted 5 years ago

Why not use tags as project identifiers? Just asking. I haven't tried it.

Posted 5 years ago

ron.warrick,
That works well for what i call " miniprojects"- simple projects of limited duration with 20 tasks or fewer. such projects don't need a hierarchical organization at all. By hierarchical I mean a project/subproject/task type organizational structure
For MAJOR projects-projects with extended time lines, many tasks, and sub projects which have to be completed in a particular sequence- you need hierarchical organization, and its damn difficult to do with tags.
I've actually come to the decision that it can't properly be done in RTM. i think the best thing to do is use a tree type outliner like TreeDB Notes and once you plan out your project, just copy/paste the tasks into rtm. You can use the general "project name' tag to ID the task, but you would look to the outliner to see where the task fits into the structure of the project.

Posted 5 years ago

Just wondering, did the developers give any reasons why they won't be implementing task hierarchies any time soon?

Posted 5 years ago

Just off the top of my head, as I am new and trying to figure it out myself:

Overall project gets a list.
Each subproject has an identifying tag
each task gets 2 tags: the subproject tag and a task tag.
Each next action task has the two listed above, plus 1 tag called NA( or whatever)

all items are on the main project list.

create a smartlist that is a search for everything with the subproject tag. This is a grouping of everything related to that subproject.

create another smart list that is a search for the subproject tag and task and NA. This is your next action list for that subproject.

Any other ideas on expanding this? I am trying to get this set up currently, but haven't had a lot of time to put into it, as I am still reading the book.

Posted 5 years ago

It still has a long way to go yet, but have you seen this?

http://www.rememberthemilk.com/forums/tips/4605/

You could set up your hierarchies like that.

Posted 5 years ago

The script(s) above mentioned is/are broken now in Firefox 3.5.

Posted 3 years ago

xxjohnboy

+1 for hierarchy. I almost switched to thinkingRock. I have spent the last day or two looking for alternatives to RTM but it is a case of the "the devil you know"

Posted 1 year ago

milkmaid88

I use priority status to sort the project name to the top. I use tags and smart lists like was recommended. While sitting in the someday list, my projects have names only with no hierarchy. Once I decide to move it into planning, it gets assigned a numbered tag 1-5 or how many ever open projects you might ever expect to have. Smart lists filter the projects into separate lists where I can begin adding tasks during the planning stage. then I title the tasks 01 task, 01a sub task. I haven't tried for a huge project yet. It is very similar to what the OP described except that my use of priority status to identify the project name eliminates one step in the hierarchy.

Posted 6 months ago

I use numbers too to create sequences. I group related tasks simply by using the same number prefix, so I may have several tasks that start with the number 3, that way they are always grouped together.

Posted 6 months ago