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

suggestions for setup

I'm trying to figure out how to organize FB as my company would use it. Let's say we have 1 product. The product is used by about 20 large clients and about 150 small clients. I'd like some users at the large clients to be able to see their bugs and no one else's (and not people from other clients). The 150 small clients don't need to have access to the system.

What setup do I do for Projects? Do I need to setup projects like "TheProduct for LargeClient 1" and TheProduct for LargeClient 2" ... 20 ... "LargeProduct for Internal" ?

To make it a little harder, I also need to keep track of bugs/enhancement requests that are reported by the 150 small clients, and tag those bugs with the client name somehow and be able to filter for smallClient62.
eric pearl Send private email
Friday, March 25, 2005
 
 
I can think of a couple ways to do this:

For the large client part, I just want to be sure that it's possible for you to have a bug in TheProduct for LargeClient A, and not have that same bug in TheProduct for LargeClientB, right?

If that is the case, then yes, I would create different projects for each client, to partition the clients.

For the smaller clients, I would either create a specific mailbox for each client, and have them submit all reports via email.  Then you can set up the mailboxes to go into the same project but different areas.  Although this means you have to have an area for each small client.

Alternatively you could put them all in the same project and I assume each client will have the same domain for their email address, so when you are looking at a case from that client, you can click the domain.com part of their email and it will show you all the cases from that domain.  Then you don't need to set up individual areas, and can use the domain as a key.
Michael H. Pryor Send private email
Friday, March 25, 2005
 
 
Wow, I'm amazed you're online at this time and working. Thanks.

For the small clients, our helpdesk typically takes calls and enters the bug for the client, so the client client email part won't work. Any other ideas for tracking the small clients?
eric pearl Send private email
Friday, March 25, 2005
 
 
> tag those bugs with the client name somehow
> and be able to filter for smallClient62

Yup, easy. From the docs:
FogBugz has two fields, Version and Computer, used to keep track of the version of your software where a particular bug was found, and the computer or computer configuration on which it was found. These fields will not necessarily make sense for every development team, so the fields can be turned off to reduce clutter, or re-named as something else if there is something else which you need to track. You can then include these fields (whatever name you give them) in your filters.

Just rename one of those to "Company". (Let's leave the word "Client" for the large companies that are created when you click Clients on the menu at the top.) Maybe rename the other to "Reported By" or "Full Name" and you can then track all the cases reported by that person at that company.

You don't want 150 areas anyway!
Dmitri Kalmar Send private email
Monday, March 28, 2005
 
 
Thanks for the suggestion. I guess I didn't think of it because the online trial doesn't allow that renaming.

Now, if only there were a pull down or validation for that field; people are going to have a field day entering:
  Parallax
  Parralax
  Paralax
  etc.
And then wonder why they can't search for the spelling they didn't enter.

:-(
eric pearl
Monday, March 28, 2005
 
 

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.