I'm open to all these, but suggest the following. BTW it's probably worth
someone researching existing project management tools
(http://en.wikipedia.org/wiki/Project_management_software) and doing a
chart to show how things are done, what features are available,
terminology, etc. for a few of the popular ones like Basecamp.

> * Context (where I can complete the task, e.g. home/work/errands/commute)

Could be useful, move to advanced in the interface.

> * Repeat (some tasks are recurring, like having to write a report once a week,
> not necessarily a calendar event)

Useful.

> * Length (time estimate)

Useful.

> * Star (maybe more of a UI thing, like gmail/toodledo)

This seems like overkill with priority.

> * Start time

We have the time when someone becomes a handler, and a due date. Not sure
this is necessary, but maybe.

> * Bug Status (new/assigned/resolved/closed/reviewed)

I would just call it "Status", and this can incoporate GTD status per
Toodledoo's example, it seems. Ideally this would not have to be updated
manually but would be automatic at least in some cases, e.g. if someone
becomes the handler for a task, they don't have to manually change this
field.

> * GTD status (see http://www.toodledo.com/info/help.php?sel=66 for examples)

See previous.

> * Dependencies

This gets into sequencing. An ability to lay out a path would be useful,
so I agree with having this.

> * Attachments

I would call this implementation, which could be a code patch or a
proposed plan of action.

Todd