Trac Integration

Trac is an open source, web-based project management and bug-tracking tool. It follows minimalistic approach in order to simplify effective tracking and handling of software issues, enhancements and overall progress. Trac sets itself apart from other bug and issue tracking tools by offering one of the best documented help sites available. It also provides wiki system, which is a great tool for project management.

Trac offers cross-platform functionality and can be run on Windows, Mac or Linux. The back-end data is stored in SQL database, which allows Trac to be hosted online too. Numerous Trac hosting solutions, both commercial and free are available such as ProjectLocker or SourceHosting.net. Another distinct feature of Trac is its integration with Subversion which provides Wiki content versioning.
Facts about TRAC
  • It is edgewall.org community of software developers 
  • It is based on the Python programming language.
  • Initial release in October, 2006

Trac and Programeter

Programeter uses Trac as a source of data about project's bugs and/or tasks. In order to add Trac to your Programeter project, click "add BUG system" (if Trac used for bug tracking) button or "add Task system" (if Trac used for task tracking) and integration dialog box will show up. Bellow you will find instructions how to add Trac as bug tracking system to your Programeter project.

Step 1: Choose Trac
From drop-down menu choose "Trac".

Step 2: Add URL, username and password
The URL is IP or web address of your Trac server with a path to the project. In order to scan your project's Trac, Programeter also needs a read-only user account. The username and password settings should be configured accordingly.

Step 3a: Add name and define bug types (optional)
This step is required if you are using Trac as a bug tracking system.

Add Name for your Trac bug system at the bottom. Then choose Bug Types from drop-down menu. Bug Types is comma separated list of ticket types that correspond to bugs. By default Trac configures it as "defect".


Step 3b: Add name and define tasks types (optional)

 Follow this step if you are using Trac as a task management system. Dialog box looks similar as from step 3a, except last field is for Tasks types and not Bug Types.

Add Name for your Trac bug system at the bottom. Then choose Task Types from drop-down menu. Task Types is comma separated list of ticket types that correspond to tasks. By default Trac configures it as "enhancement, task".

Step 4: Verify integration status
Status of your bug tracking tool integration is set to "configured". Initial scanning and analysis is resource consuming process and can take in certain cases up to few days, so please be patient. Status will be changed to "monitoring" meaning, now you can access reports for your project. If the status is marked "error", please contact our helpdesk.

Reports based on Trac Data scan

Programeter has three types of reports which rely on data pulled from Trac. Firstly, there is a report on completed tasks and bugs (belongs to Effort angle) which shows the correlation between completed tasks and fixed bugs.

Secondly, features burn-up and tasks statuses reports from Scope angle. These reports display how project scope is changing through the lifetime of the project. They also are used to evaluate task execution effectiveness.


             
Thirdly, bugs statuses and product quality reports from Quality Assurance angle. These reports indicate the effectiveness of bug handling and the correlation between the number of total completed tasks and total bugs through the project timeline:
           

If you would like to take a look at other charts generated by Programeter, please take a look to product page.
Olark Livehelp