FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

How to organize projects?


Developing a product could mean the product is one application that could map directly to a FogBugz project and have several areas and releases. On the other hand it could mean that several different applications make up the whole product. How can you map this in FogBugz?

For example. I have product BestAppEver v2.0 and this has a couple of different applications:

BestAppEver Server v2.0
BestAppEver Desktop v2.0
BestAppEver Mobile v1.9

How would you organize that in FogBugz? Would you have one project named BestAppEver with one area per application? Would you have one project per application? What is the best way not to loose the whole picture of "the product" but at the same time track each application separately?

Thank you,
Petros Amiridis Send private email
Monday, September 17, 2007
I manage an application here whose architecture is that of a core program and multiple plugins. The core program and the plugins all have independent release schedules, so they have different projects in FogBugz.

I have them all assigned to a department so that I can filter on them.
David Thompson Send private email
Monday, September 17, 2007
Personally I would have 3 separate projects, especially as per your example each product could be at a different version, and presumably has a separate code base.

You could then use a global release (FixFor) to "bundle" the apps together, or another project that deals with any possible bundling, marketing or sales issues etc.
Ian M. Jones (CaseDetective) Send private email
Monday, September 17, 2007

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.