|Version 26 (modified by k0s, 5 years ago) (diff)|
track hours spent on tickets
Table of Contents
The goal of this plugin is to help keep trac of hours worked on tickets.
Goals of TracHoursPlugin
- Instead of adding hours via the comment system, there is a separate view for hours:
- /hours is a management view. This view displays the hours for all tickets for the last week (by default) in a way that combines the query interface for querying tickets and the timeline display for hours on the tickets in the time period.
- query filters are available to find hours for people, hours for tickets of a certain component, etc;
- a view for /hours/<ticket number>; this displays the accrued hours for a particular ticket with a timeline-like view, but should also allow adding of new hours (by default, on "today", but this should be changeable via dropdown menus for day, month, year, etc), editing previously entered hours (amount, date, description) and deleting previously alloted hours
- the view at /hours/<ticket number> by default will only display the hours on the ticket. If you have the TICKET_ADD_HOURS permission, this view allows adding/editing of one's own hours on the ticket If you are a TRAC_ADMIN, you should be able to add/edit/delete others' hours as well
- the default query period is the last seven days
- Hours are uniquely assigned to tickets and people (required fields)
- hours may have a description, which should be displayed in the applicable views; if a description is provided, the hours and description are logged to ticket comments
- /ticket/<number> has a link to /hours/<number> as the total hours field so that a user can add and view hours for the ticket
Hour tracking and estimation is most useful when the following questions can be answered:
- How much time has been spent on a project?
- How much time remains in a budget (estimate for a project)?
- How much time have we committed to for the next time period ?
- How much time is a developer committed to over the next time period?
If we put hour estimates on tickets, assign tickets to people, associate tickets with milestones, and give milestones due dates, a good time tracking plugin could generate reports to answer those questions.
For other trac time-tracking solutions, see http://trac.edgewall.org/wiki/TimeTracking
The TracHoursPlugin exports RSS from the /hours handler. This has been utilized in consumption to provide hours reports across projects sharing the same parent directory. If trachours.multiproject is enabled, then /hours/multiproject will become a handler front-ending hours reports throughout the project and a link to this will appear on the /hours page to /hours/multiproject.
The multiproject report breaks down hours by project and worker giving row and column totals. If there are no hours for a project then that project will not be shown.
How to Use TracHours
Installing and Enabling TracHours
TracHoursPlugin is enabled like any other trac plugin:
- download and install the plugin; see plugin installation instructions at http://trac.edgewall.org/wiki/TracPlugins#InstallingaTracPlugin
- enable the plugin. Use either the webadmin interface or add the following lines to the trac.ini file:
[components] trachours.* = enabled
- add give users the permission TICKET_ADD_HOURS
- you will need to run trac-admin <env> upgrade in order to create the correct database tables
The TracHoursPlugin requires python at least 2.4
A preliminary path to 1.0 is outlined here: http://www.openplans.org/projects/topp-engineering/lists/trac/archive/2009/01/1231168734645
Note: The TracHoursPlugin requires python version at least 2.4
See also the trac plugin installation instructions at http://trac.edgewall.org/wiki/TracPlugins#InstallingaTracPlugin
-  by rjollos on 2014-12-08 20:36:36
0.6.0dev: Encode headers when exporting as CSV to fix traceback. Fixes #10233.
-  by rjollos on 2014-10-10 06:03:10
0.6dev: Avoid exception when hours value is invalid.
-  by rjollos on 2014-10-10 06:03:00
0.6dev: Protect against exception when Total hours custom field is missing.
Original developed at The Open Planning Project