4.7 was the last time I used it. There are some key features that pushed me that way * Ability to invent my own case states. * Abiltiy to assign work to others. * Really intuitive filtering logic. Using RTE's like tinymce would break the project every time it was edited because of the mixing of the need for body fields and state fields etc. I have a lot of respect for Derek and the maintainers of Project, but when I asked them on the issue queue they suggested that they didn't really expect it to be used outside of drupal, that's when I found casetracker. It's alos a pretty sweet module with views integration etc. My 2 cents. -----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Greg Knaddison - GVS Sent: Thursday, February 07, 2008 12:09 PM To: support@drupal.org Subject: Re: [support] Assigning project issues On Feb 7, 2008 5:37 PM, Metzler, David <metzlerd@evergreen.edu> wrote:

Seriousely, if you're using this outside of drupal, you might consider casetracker instead. I started with project, and moved to case tracker for similar reasons. It has this functionality. There's a lot of extra CVS stuff etc in project that gets in the way. Project has a lot of Drupal.org specific stuff in it.

When was the last time you used Project module? I use it currently and don't notice either of these issues. I used it under Drupal4.6 and it didn't have the problems then, even, but it wasn't as nice then as it is now, of course. I suggest you re-evaluate it because it no longer has either of those problems (being overly tied to cvs nor overly tied to drupal.org). It doesn't have the ability to assign issues to another person though there are patches in the queue to allow this which need reviews and help. Regards, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg -- [ Drupal support list | http://lists.drupal.org/ ]