Display project statistics on code, wiki and tickets
This plugin shows project statistics about Subversion, wiki, and ticket system of your Trac environment. It adds a Stats tab to the navigation bar of the Trac project.
- Recent activity (last 30 days) showing top 10 developers, projects, and paths within the repository.
- Detailed statistics of source code development:
- Total files by time
- Commits by time, author, month, day of week, hour of day
- Recent commits
- Activity by time, author, project, file type, change type
- Most active paths, files
- Commit cloud, built from checkin comments
- Detailed statistics of Trac wiki pages:
- Total pages by time
- Edits by author
- Latest wiki pages changed
- Most active wiki pages
- Largest wiki pages
- Detailed statistics of Trac tickets:
- Open tickets by time
- Tickets by author, component
- Most active tickets
- Oldest open tickets
- Latest tickets reported, changed
- Drill down by author or path within the repository for more information.
Tag cloud based on ticket activity
This plugin works with SQLite, MySQL and PostgreSQL database backends. This plugin has been tested with Subversion, Mercurial and Git version control systems.
See GitHub for more details and the source code, or to report issues or request features.
You can install it with:
$ easy_install tracstats
It needs to be enabled in your
trac.ini file as follows:
[components] tracstats.* = enabled
STATS_VIEW permission is used to control access to the statistics pages. Under Permissions add this permission to the users who should have access to the project statistics pages.
In addition, an optional "project root" within your repository can be configured as the base for all projects and source code statistics:
[stats] root = path/to/projects
If you use Git, ie the GitPlugin for Trac, and are not able to see any of the code statistics, you likely need to configure it to cache the repository to make it work:
[git] cached_repository = true persistent_cache = true
You might need to run
trac-admin <project-env> repository resync <reponame> after the change.