I've been in the habit over the last few years of using e-mail to keep track of tasks at work. It's basically the simplest of bug tracking tools (apart from a text file) and supports most of the operations you would find in an actual bug tracking tool.
- The subject line of the e-mail is implicitly the bug identifier. Any e-mail client that groups messages by conversations will automatically keep things organized for you.
- Adding correspondence is as simple as replying.
- You can add attachments as well.
But it has some advantages as well,
- Available anywhere you have access to your e-mail, such as your phone, so it's easy to add a thought as a reply without having to log into your work environment.
Of course this doesn't replace an actual bug tracking system for tracking software bugs or working with a team, but I find it quite effective for tracking tasks and issues when working on something over a period of time.
For example, over the past two days I have been working through a fairly tricky Android NDK issue. Whenever I need to put it down for a bit, due to a meeting, or commuting home at the end of the day, I reply to the e-mail thread I have going with myself about the issue and record my latest progress, thoughts on ongoing technical challenges, and my planned next steps.
This has made it super easy to pick the thread up again when I next sit down to work on it. And since it's in e-mail, if I suddenly have an epiphany while doing dishes or something in the evening, I can quickly add a reply to my e-mail thread rather than having to log into work from my computer or deal with writing down on a piece of paper and then remembering to take that with me the next day.