What Does Everyone Use For Task/Project Tracking?

JerBear0 writes "I work as the sole IT employee at a company of about 50 people. I handle programming, support, pretty much anything that is IT related, or even that plugs in. As seems to be true with many small companies, the priorities seem to shift quite frequently. As a result, I've always got multiple programming (both new systems and improvements/changes to existing systems), integration, research, maintenance tasks/projects on my To Do list, in varying stages of completion. At any given time, I need to be able to jump back to one of these items and pick up where I left off. I am currently using Outlook Tasks, and then end up referencing my notebook and email for those dates to figure out exactly where I left off. It works, but not well. If it's been a while, I'll end up losing an hour or two just tracking everything down. I looked at using MS Project / OpenProj, but they want an individual file for each project, and I want at least the project/task list all on one screen. Essentially what I'd want would be a Task List on steroids, allowing for hierarchical subtasks, attachments, and prioritization. Ideally it would be a desktop app, but a locally-hostable web app would be okay. In some of these projects I may want to include proprietary information, which I really don't want floating out in the cloud outside of my control. I know I'm not alone in this problem, so what do you guys (gals) use to address this?"

Comments

Emacs org-mode

[Enfors]

Are you an emacs user? If so, then I definitely recommend org-mode: http://orgmode.org/

It's notes mixed with todos on steroids (which themselves are on steroids). There's nothing it can't do. Check it out.

There's a Google tech video about it here: http://www.youtube.com/watch?v=oJTwQvgfgMM

Re:Bugzilla and Wiki

[kobaz]

It's also a mess to maintain, since it's written in Perl.

Nice troll!

"I hate X because I can't use it properly". "I hate X because other people can't use it properly".

It's a pretty common misconception that a *language* makes things hard to maintain. I've seen horrible C code, I've seen excellent C code. I've seen horrible PHP code, and I've seen excellent PHP code. And of course I've seen some amazing Perl. It's a matter of development experience combined with time and effort of the authors, that makes a project is easy to maintain or not... not the language.

If your bugzilla guy is a Python expert, then maybe his skills are lacking in Perl... which is why it's hard to maintain... just a thought.