This would be a big help.

I have been prefixing codes to task names to get around exactly this problem.

The other thing that would help would be capability to copy, in addition to moving, tasks from one list to another. This would let a user set up a standard template of tasks for a project / job / client etc and then quickly populate a new list.

tm, just realized, I will still need the prefixes. I try to work from the Google gadget and stay focused on the Overdue / Today items. In fact I purposefully keep due dates unassigned on sub-task / checklist type items so that they won't show up on my GPHP until I start work on them.

Also just double checked a smart list task. If you hover over the task the List shows at the top of the details panel at the right.

I generally only use RTM directly at the start of a day.

Owyn, related to your 1:26am post re copying tasks... while I agree that copying would be useful, here's a suggestion for a workaround in the mean time - assemble the template in email, and each time you need to recreate the set, resend it to yourself to your bulk email import address.

More on this here: http://www.rememberthemilk.com/help/answers/sending/importemail.rtm

Hope that's of some help,
Ran

Thanks Ran

I looked at that already and ran into several problems with the function.

1) Limited to task name attribute. Needs a richer syntax.

2) Tried setting it up with local text library with copy and paste to Gmail. This works but was a bit cumbersome and not portable between systems. I am considering doing this with a web accessible personal wiki page.

3) I have not found an easy way to set up a message template in Gmail.

Just got an API key from Emily. One of the items I want to try with the API is a richer import / export facility.

You are right about #1, but at least once the task names are into RTM, you can use multiedit to assign what you want pretty quickly.

As for #3, could you set up a label "RTM Templates" and then just pick and choose among them, perhaps naming each message with a specific enough subject that retrieval could be pretty easy?

Anyway, that's the end of my bright ideas. I wish you luck with your API key, and please keep us informed of your progress.

owyn... thanks, yeah, that is what I'm doing. I have a 3 char code for each list.. but seams like there must be a better way..

If you do a smart list, the origin does show on the weekly planner.. but no where else..

tm: Thanks, I had not tried Print from a Smart List.

ran: The problem with Gmail is that you can not re-send a message. Forward, no problem, but then it is in the wrong format for RTM.