[email protected] Subject: Plain English Arguments Body: whatever else we might need.
For example:
Email: [email protected] Subject: Today at 5PM Body: Buy milk! Also, don't forget to buy some KY, and a lawn chair.
The problem with other systems is they usually try to put the arguments into the email.
I'm working on a todo system as well.
Email: [email protected] Subject: Name of Todo List Body: One Todo For Every line Of the email
Sends you a reminder every so often, and you can reply back with what you've accomplished by putting a - in front of the item.
Their are other ideas being worked on. One I'm trying to find time to finish up is a daily habit system.
It would email you in the morning reminding you what you want to do every day, and then at the end of the day, it will email you, asking you for an update on how you did, and you could reply back, etc.
It also has a wiki and file storage, and folk started using these without them ever being mentioned. Kinda supports the idea of: give folk the tools and let them get on with it.
(I am not recommending Redmine, per se, it was just what I grabbed to quickly bring sanity to an out of control situation at the time. It's not bad, though.)
Seems like it should have been done before though.
My impression is that a lot of bug tracking tools integrate with email (e.g. lighthouse, surely others), but usually it's a minor support role to the webapp, instead of being the main focus.
Issue commands via subject line.
Add / Update / Close Task
Assign / Transfer Task
Timesheet Task
Share Task
User could add whatever they want to save about a task in the email body.
Archive the emails centrally and provide full text search.
Hook into the customer database and tag the content.
Centralize knowledge in the organization.
Use a tool everyone already owns and understands.