Usage ScenariosBelow are some typical BUGtrack usage scenarios. You may follow these scenarios as is, or in any combination. Simple ApproachThis is the simplest scenario suitable for most projects. All company's offices are using the same license and the same customer lists. 
| Advantages: | Points to consider: | - All project-related information is located in one place.
- Affordability
| - Customers have access to all bugs/issues.
- More difficult administration because all users and customers in the same account. Different companies will not be able to keep some projects private and inaccessible to others.
|
Separate Customer Team from Developer TeamUse this scenario when you don't want to give your customers access to your development process and team, when you have several customers on the same project and they shouldn't see each other, or when you don't want your development team to interact with customers. 
| Advantages: | Points to consider: | - Customer's issues and developer's issues are secure and separated from each other.
| - Requires some effort from Management to keep consistency between projects.
|
Anonymous accessUse this scenario when you expect to receive bug reports from a large amount of anonymous people. 
| Advantages: | Points to consider: | - Custom Form may be customized to have your company's website look and feel.
| - Requires some effort from Quality Assurance to filter duplicate issues from user's project.
|
Common Project Development
This scenario is ideal when two or more companies work together on a common project but they also have private projects related to this development.
Both companies are buying separate licenses (Online PRO Pack is required at least for one of them in order to initiate sharing). Common projects may be shared between companies or between customer and companies. One project can be shared between many accounts.
| Advantages: | Points to consider: | - You work with common projects the same way as with private projects.
- Separated user access administration for common projects inside each license.
- Companies and customers are completely independent and working with each other using Project Share. All offices and customers with separate licenses may have their private projects invisible to others.
| - At least one company must have PRO Pack in order to initiate project sharing.
- More expensive.
|
| 
