While it may not be obvious to the casual observer, this is actually an all new levelos.com. As a developer, I am ashamed to say that I have not always given my own site the attention it deserves. You know the old phrase, "the coblers kids where no shoes," or something like that at least. In anycase, over the past year or so, I have become enamored with Drupal, an amazing website platform for building anything from a simple blog to a complex web application. Kudos to the amazing job the Drupal community has done - I hope I can find a way to contribute back. Some of my recent successful projects, including The Portland Opera, MomHub, and Newsvetter were all developed on the Drupal platform.With the recent launch of MomHub, Hal, my partner on the project, and I needed a better way to track issues and bugs as we release the site to a broader audience. I use activeCollab, the open source version since they are now commercial, for project management, but it's task system was not developed enough. There are several open source tools available, like Bugzilla and Trac, but I opted to use Drupal's Project and Issue Tracking modules. Rather than launch a standalone site for this, I just rewrote levelos.com in Drupal and implemented the project and issue tracking functionality. It's a real credit to Drupal, and how much I have learned over the past year, that I was able to do this in one very late night. I'd love to hear if you have any other ideas for bug tracking, or how the new site is working out.For some time, I have also wanted to treat my site as more of a blog, and less of an agency site, and now I can do that as well. Most of my blog entries will be promoted to the front page feed, but I will also publish new projects there. You can access just the blog posts here.

New site
lookin' good. My site has the same problem (I always mean to give it more attention, but never have enough time.) I like the theming on the menu bar, at the top.
Drupal's tracking stuff is pretty cool, but it seems really focused on CVS (I need to play with it a bit more to be sure) I have alot of issues with CVS. It is really hard to change things around, and it chokes on alot of things that SVN seems to handle without issue, plus I like SVN's branching system better. For my own stuff, I use Trac and SVN, as they work really well with each other, and you can get some pretty awesome Eclipse integration (Mylyn: contextual bug listing in in a panel your IDE! Subclipse: SVN versioning and annotation when you save, etc)
It may be possible to use Trac with Drupal, though:
http://groups.drupal.org/node/1047
Thanks for the feedback
Thanks for the feedback David - appreciate it. I ended up choosing Case Tracker combined with Organic Groups for issue tracking. Case Tracker is a re-write of the project module, with issue tracking built in, and it is more user friendly and less focused on software development. It also has email notifications built in, which is critical. OG is necessary to restrict access to projects to groups of individuals. So I setup my groups as clients, and then added projects to the client areas. I am just getting started, but this has been working well so far.
I like Trac, and considered using it, but since it is written in Python and I rely on a shared server which doesn't support, it was ruled out. I am also not familiar with Python, so didn't want to lose the ability to easily make some hacks. Maybe I should reconsider, though.
SVN+Drupal
That makes sense. I think my eclipse dependencies make it a special case. It sounds like you found a good solution, especially considering your shared hosting situation.
After reading the first message, I started thinking about using SVN with Drupal, and wondering how much work it would actually take to get it useful, and integrated into Eclipse+web summaries (for clients and devs who use Vim or whatever) I found:
http://drupal.org/project/subversion
It looks sort of broken from the demo site (svn diffs on revisions display nothing, and RSS message summaries are not working) but this may be a good starting point for writing something that works well with SVN. It appears they are using Project.
I also found:
http://drupal.org/project/versioncontrol
which the developer of the subversion module is working on integrating with. It is a general API for connecting to a VCS. This would be an even better candidate for mylar integration, because you could use any system that works with it (they have CVS working, currently) and the drupal-RRS-parsing-glue would be the same. They have RSS feeds for issues working, but it appears that follow-ups are not included.