[consulting] Issue tracking for clients

[Boris Mann]

On 10/23/06, Khalid B <kb at 2bits.com> 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.
>
> There is case tracker which is more generic than just software
> development, but I have no used.
>
> There are other non-Drupal solutions, such as Trac http://trac.edgewall.org/
> but not sure how suited they are in more private settings.

We are heavy users of trac for *development* ticketing...it is not
really appropriate or easy enough for clients.

You can run multiple instances of Trac off a single codebase if you
need separate repos.

> Third party hosted services include things like http://basecamphq.com, and
> a smaller http://sidejobtrack.com and http://www.secondsite.biz

We use Basecamp for project management. This is also usually where
client "tickets" go -- they don't know enough to file good tickets in
any case.

I would like to re-examine replacing Basecamp with a Drupal instance
as we did pre-Basecamp. Drupal 4.5 + OG wasn't quite polished enough
at the time :P

Case tracker looks to be a good general solution, but for that matter,
if you use external development ticketing as we do with Trac, just
organic groups may very well work.

-- 
Boris Mann
Vancouver 778-896-2747
San Francisco 415-367-3595
Skype borismann
http://www.bryght.com