FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

Managing clients and projects as... well projects

We are a software company that has about 150 clients. Traditionally we have always loaded each client as a "Project" in Fogbugz so we can (1) keep track of the issues reported by each client and (2) assign an account manager as the primary contact to each project/client so that they are aware of what issues their client is experiencing as they get emailed as each case gets assigned to their client.

This has worked really well for us for a number of years qs a CRM system. It has meant though that our projects e.g. technical projects have been run in Pivotal Tracker. This has a number of problems as internal feature requests are loaded in Pivotal, but customer reported bugs/feature requests are normally emailed into Target by a client and then have to be manually copied and pasted into Pivotal.

We would like to standardise on Fogbugz so that client projects and technical projects are all run in Fogbugz.

However, I'm interested to hear suggestions on how we can split out "client projects" from "technical projects" so that the following is achieved:

(1) We can split them into separate menu items on the default.asp?pg=pgOldMainMenu page i.e. a list of client projects and then a list of technical projects. A developer wants to be able to see the open technical projects in one look and not have to pick them out of a 150 item long client project list

(2) That the client projects still assign the account manager as the primary contact so that they can be kept in the loop on the issues their client faces

(3) That a bug or issue reported by a client can be "allocated" to a technical project without loosing its link to the client project. This will allow us know that "Bug xyz is occurring in product abc on client 123's site". That the bug can be "allocated" to product abc so that when fixed it gets into the release notes. But at the same time when closed, can then notify the client that the bug has been resolved. Just editing the case and changing the project won't work as someone will forget and just close the case in the technical project, and the client will never know their issue has been resolved

I've used the term "project" for both client projects and technical projects, but possibly there is a better was to do this. Maybe a custom field? I don't think groups will work as it doesn't solve the problems listed in 1-3.

Any ideas from other users out there?
Rowan Send private email
Thursday, October 29, 2009
 
 
Can you also post this on fogbugz.stackexchange.com?

I'd do it for you, but then it wouldn't be from you.
Rich Armstrong Send private email
Thursday, October 29, 2009
 
 
Rowan Send private email
Thursday, October 29, 2009
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.