- Using a Plugin (Trac ≥ 0.10)
- Trac 0.9.x, 0.10 (using custom ticket fields)
- Known Issues
- Trac 0.8 (extending the data model)
Support for basic time tracking is an oft requested feature (#710), but has not been implemented in Trac core. There are ways to enhance the ticket system with the desired functionality and this page is meant as an overview of working solutions and as a howto.
- wiki:PluginList#ProjectTimeManagementTicketSystemExtensions recommends to use a combination of several plugins, each one covering a partial functionality of what one needs for time tracking.
- There are also other possibilities by using other plugins. So far, solutions are available and are briefly described below:
- Note 1
- For more and up-to-date details visit plug-ins page.
- Note 2
- For an updated and related plug-ins list at Trac-Hacks: timingandestimationplugin.
- Note 3
- Patches are unofficial, please do not report bugs through the Trac ticket system. Instead contact the trac user mailing list or Steffen Pingel.
Using a Plugin (Trac ≥ 0.10)
The Timing And Estimation Plugin works much the same as the Trac .9.x custom fields approach, except that it should be easier to install and provides a bit more in depth reporting. It also contains a ticket change daemon that allows you to add time and display the total. Also see the demo version, so you can try and decide if it is right for you, as well as report bugs.
The TracHours plugin provides a different approach to time tracking (for Trac 0.11 only). Instead of adding hours via a ticket field, separate views are available for adding and reporting hours.
The BudgetingPlugin provides splitting the work-effort for a ticket in several smaller pieces. You can configure tasks (for example implementation, documentation, etc.) and assign users.
The WorkLog Plugin provides the ability to 'clock in' and 'clock out' and displays which users are currently working on tickets. If either the TimingAndEstimationPlugin or TracHours plugin is being used, spent time will be recorded to a ticket when the user 'clocks out'.
The EstimatorPlugin allows you to enter upfront estimations as to how long the completion of a ticket is going to take.
Trac 0.9.x, 0.10 (using custom ticket fields)
A less invasive way than modifying the database as required for Trac 0.8 is to add time tracking through TracTicketsCustomFields. Custom fields are meant as an extension mechanism that allows to store additional data with tickets without changing the underlying data model.
This patch requires a few steps for installation:
- Patch Trac to provide a progress bar in the Roadmap view.
trac.inifor each project to add custom fields.
- Add a ticket query (optional).
- Use a Subversion commit hook to log spent time (optional).
Download and apply the time tracking patch:
- Download and unzip/untar Trac (see TracDownload)
wget http://ftp.edgewall.com/pub/trac/trac-0.10.tar.gz tar -xzvf trac-0.10.tar.gz
- Run patch from the created trac-0.10 directory:
cd trac-0.10 wget http://steffenpingel.de/files/patches/trac/trac-time-tracking-0.10.diff patch -p0 < trac-time-tracking-0.10.diff
- (Re)install Trac (see TracInstall):
Add the following section to your
trac.ini file in your project's configuration directory, see TracIni. This needs to be done for each project that you want to enable time tracking for:
[ticket-custom] tt_estimated = text tt_estimated.label = Time planned tt_spent = text tt_spent.label = Time spent tt_remaining = text tt_remaining.label = Time remaining
Adding the query (optional)
Open your Trac project in a web browser and goto "View Tickets" → "New Report". You may have to grant the
REPORT_CREATE permission first. Enter a title like "Time Tracking" and the following query:
SELECT DISTINCT id AS ticket, (CASE WHEN pl.value ISNULL THEN '' ELSE pl.value END) AS planned, (CASE WHEN s.value ISNULL THEN '' ELSE s.value END) AS spent, (CASE WHEN r.value ISNULL THEN '' ELSE r.value END) AS remaining, (CASE WHEN ((s.value + r.value) - pl.value) = "0.0" THEN ' ' ELSE (s.value + r.value) - pl.value END) AS accuracy, milestone AS customer, summary, component, status FROM ticket t, enum p LEFT OUTER JOIN ticket_custom pl ON (t.id = pl.ticket AND pl.name = 'tt_estimated') LEFT OUTER JOIN ticket_custom s ON (t.id = s.ticket AND s.name = 'tt_spent') LEFT OUTER JOIN ticket_custom r ON (t.id = r.ticket AND r.name = 'tt_remaining') ORDER BY milestone
Using PostgreSQL with psycho
PostgreSQL has a few wrinkles and time intervals are not as hard to use:
SELECT DISTINCT id AS ticket, pl.value::interval AS planned, s.value::interval AS spent, r.value::interval AS interval, ((s.value::interval + r.value::interval) - pl.value::interval) AS accuracy, milestone AS customer, summary, component, status FROM enum, ticket t LEFT OUTER JOIN ticket_custom pl ON (t.id = pl.ticket AND pl.name = 'tt_estimated') LEFT OUTER JOIN ticket_custom s ON (t.id = s.ticket AND s.name = 'tt_spent') LEFT OUTER JOIN ticket_custom r ON (t.id = r.ticket AND r.name = 'tt_remaining') ORDER BY milestone;
SELECT DISTINCT id AS ticket, (CASE WHEN pl.value IS NULL THEN '' ELSE pl.value END) AS planned, (CASE WHEN s.value IS NULL THEN '' ELSE s.value END) AS spent, (CASE WHEN r.value IS NULL THEN '' ELSE r.value END) AS remaining, (CASE WHEN ((s.value + r.value) - pl.value) IS NULL THEN '' WHEN((s.value + r.value) - pl.value) = "0.0" THEN ' ' ELSE (s.value + r.value) - pl.value END) AS accuracy, milestone AS customer, summary, component, status FROM enum p, ticket t LEFT OUTER JOIN ticket_custom pl ON (t.id = pl.ticket AND pl.name = 'tt_estimated') LEFT OUTER JOIN ticket_custom s ON (t.id = s.ticket AND s.name = 'tt_spent') LEFT OUTER JOIN ticket_custom r ON (t.id = r.ticket AND r.name = 'tt_remaining') ORDER BY milestone
Using a Subversion commit hook (optional)
contrib/trac-post-commit-hook script is a very convenient tool to interact with Trac's ticket system on commit. It allows to modify time tracking values and ticket state through special commit messages.
- Create a script
hooks/post-commitin your Subversion repository with the content below (modify TRAC_ENV to point to your local Trac project).
- Set the executable bit:
chmod 755 hooks/post-commit.
REPOS="$1" REV="$2" LOG=`svnlook log -r $REV $REPOS` AUTHOR=`svnlook author -r $REV $REPOS` TRAC_ENV='/var/trac/test' /usr/bin/python /usr/share/trac/contrib/trac-post-commit-hook \ -p "$TRAC_ENV" \ -r "$REV" \ -u "$AUTHOR" \ -m "$LOG"
You can now use special keywords in your commit message to modify Trac tickets. The available commands are:
|refs #id||Adds a reference to the ticket's Changelog|
|closes #id||Closes the ticket|
The time spent and the estimated time remaining are specified in parenthesis. Legal units are either hours (h) or minutes (m):
|(spent xx h)||Adds xx to time spent and decreases time remaining by xx, |
|(spent xx h, rem yy h)||Adds xx to time spent and sets time remaining to yy.|
contrib/trac-post-commit-hook for details (after applying the patch).
svn commit -m 'Added time tracking, refs #1 (spent 4h, rem 1h)'
This adds an entry to the Changelog of ticket #1, increases the time spent by 4 hours and sets the remaining time to 1 hour.
svn commit -m 'Added time tracking, closes #1 (1h), refs #2 (2h, rem 30m)'
This closes ticket #1, increases the time spent by 1 hour and decreases the remaining time by 1 hour. It adds an entry to the Changelog of ticket #2, increases the time spent by 2 hours and sets the remaining time to 30 minutes.
Click to enlarge.
Patches for older version of Trac can be found at http://steffenpingel.de/files/patches/trac/.
- The patch has been adapted for Trac 0.10
- The patch has been adapted for Trac 0.9.6
- Significant enhancements to the milestone page and the post-commit-hook (please see the documentation for the new syntax) have been contributed by Magnus Sandberg:
- The milestone page now show time tracking progress bars for "Ticket status by x"
- The commit hook can now handle different spent/remaining values for multiple tickets
- Tooltips have been added to the time tracking progress bars
- The patch has been adapted for Trac 0.9.5
- Some of the rendering related label tweaks have been removed
- The patch has been adapted for Trac 0.9.4
- The difference between estimated and spent + remaining time is now displayed
- The progress bar is now displayed when spent work is less than 1 h
- Fixes for the progress bar by Michele Franzin have been merged
- The patch has been adapted for Trac 0.9.3
- Patches for PostGreSQL compatibility by Fredrik Corneliusson and Matthew Good have been merged
- The patch has been adapted for Trac 0.9.2
- First release for Trac 0.9 stable branch
- I couldn't see the second milestone bars so hacked the roadmap.cs to see them … until I realized that using units (4h instead of just 4 …) was the problem. All working now, very nice, many thanks.
- If your ticket doesn't have a time planned and/or time remaining set, and you spend time on a ticket, you end up with negative time values, which messes up time planning by having a net time spend of zero.
Trac 0.8 (extending the data model)
This patch is for Trac version 0.8.
A patch has been posted to #1005 that adds two new fields to the ticket table, "Planned work" and "Actual work", that can be edited in the ticket view. It also extends the Roadmap with a progress bar that displays how much work has been done and how much remains.
trac-roadmap.png (24.4 KB) - added by 10 years ago.
Roadmap with Time-Tracking patch
trac-timetracking-report.png (54.6 KB) - added by 10 years ago.
Ticket report displaying Time-Tracking progress
trac-roadmap-thumb.png (16.5 KB) - added by 10 years ago.
Roadmap with Time-Tracking patch (thumb)
trac-timetracking-report-thumb.png (39.7 KB) - added by 10 years ago.
Ticket report displaying Time-Tracking progress (thumb)
CustomFieldsRev2827.patch (4.6 KB) - added by 10 years ago.
Patch to add numerical custom fields
time-tracking-milestone.png (35.3 KB) - added by 9 years ago.
Milestone page showing ticket status by type
CustomFields0.11Rev7651.patch (4.9 KB) - added by 7 years ago.
Integer Custom ticket fields patch for Genshi
Download all attachments as: .zip