Introduction
Imagine you are using open source tools for supporting your software creation process. Typical software tools for this purpose are:
- A source-repository like CVS or Subversion
- A ticketing system like Trac or Bugzilla
- A time tracking tool like Tutos, Kimai or, if you're unlucky, some simple spreadsheets
Teamtrac is the tool that provides the glue between these tools. It can be used to provide statistics and evaluations across the boundaries of each of these tools.
Do you need to know, how much time it took to solve a ticket? Teamtrac creates a link between a ticket and time recordings of another tool. Do you want to know, who of your developers will take more time than expected to fix her tickets? Teamtrac can work with milestones and expected workloads and tells you where organizational problem lie. Teamtrac allows also the separation of mainstream, milestone-based development and project-related short-term tasks.
It is mainly used to integrate with existing tools rather then forcing companies to replace existing tools.
Web-based
Teamtrac is completely web-based and has been written in PHP. The use of the
Smarty template engine ensures maximum flexibility regarding output formats.
Extensible
Teamtrac is designed to be modular. Arbitrary ticket systems, time recording tools and project management tools can be integrated. The architecture of Teamtrac is explained
on a separate page.
Target Audience
If you use a tool that already integrates a code repository, a trouble report system and time recording tool, Teamtrac is probably not of any use for you. In case you use different tools for these tasks, you might want to use Teamtrac to correlate these tools.
Check out the
screenshots section to learn more about the power of Teamtrac.
