Use tasks to represent the state of an object to be tracked (project, bug, defect, version, component, module, etc).
The system supports a task hierarchy, which means that projects can contain subprojects and the latter can contain issues. This makes the user interface much easier: if you know how to create a project, you know how to create bugs. If you can create a workflow and set security rules for a certain project, it means you can create workflows and set security rules for project groups and even for issues.
All the created objects (filters, workflows, custom fields) can be inherited, which means you do not have to declare the same custom fields and workflows for each new project. It is enough just to create a new project and it will automatically inherit all the properties common for this project group. You can also enhance the inherited objects to make them fit the specific project. To create a global object available for every task in the system, you must create an object attached to the root task.
Suppose some bugs appear in versions of your software both for Windows and Linux. The versions for different platforms are being developed by different teams and you need to track the bug fixes individually for every version. There are two common ways to ensure this:
In TrackStudio you can create several versions of each task (in fact, each of them is a lower level task of a special kind) and set up individual properties (handler, access rights etc.) for each of them. You will be able to view both the general information on the task (e.g. the total time spent on fixing the bug in all versions) and the version or configuration-specific information (e.g. the list of all bugs not yet fixed in the Windows version or the list of overtime issues).