[consulting] Issue tracking for clients

[Dave Cohen]

I set out to do this sort of thing with Drupal's project module, but I found 
it heavyweight and with a lot of features aimed at CVS, which I did not need.  
So I set out to see what I could put together using contrib modules.  I'm 
pleased with the result.  I use it on my own site, www.dave-cohen.com and I'm 
thinking about developing it into a supported service for other consultants 
to use.  Here's a brief summary of how its put together...

Custom node types called Project and Issue.

Category module (a Project is a container).

Cac_lite module for access control.  If you visit my site you can see some 
public projects, but most projects and issues are hidden so only my clients 
can see them.  This is why I developed cac_lite (It comes with category 
module, in the contrib directory).

Workflow module to keep track of issue state.

comment_terms is a module I wrote so that when adding a comment to an issue, 
the user can also adjust the workflow state, categories and other attributes.  
This makes a comment on my system similar to a followup in the project 
module.  Comment_terms uses some other module apis which are not meant to be 
public, so I wont check it into drupal cvs, but it's in my sandbox and you 
can read more here: http://www.dave-cohen.com/node/1008 (That page is an 
example of a project on my site).

Here's an example issue: http://www.dave-cohen.com/node/1267.  If you log in, 
you can visit the add comment form, which will show how comment_terms prompts 
for fields (ie status, severity, assignee) when adding a comment.

-Dave


On Monday 23 October 2006 13:33, Khalid B wrote:
> Hello
>
> Drupal already has the project module that is used on drupal.org for
> issue tracking. This is suited for open source community projects.
>
> But for tracking issues for a site one builds for a client, you don't
> want Client A to see Project B for example.
>