| 3 | | [[Include(https://svn.openplans.org/svn/trac/TracHoursPlugin/README.txt)]] |
| | 3 | == TracHoursPlugin == |
| | 4 | |
| | 5 | The goal of this plugin is to help keep trac of hours worked on |
| | 6 | tickets. This is done in response to |
| | 7 | TimingAndEstimationPlugin, but tailored to suit present needs: |
| | 8 | |
| | 9 | * Instead of adding hours via the comment system, there is a separate |
| | 10 | view for hours: |
| | 11 | |
| | 12 | - {{{/hours}}} is a management view. This view displays the hours for all |
| | 13 | tickets for the last week (by default) in a way that combines the |
| | 14 | query interface for querying tickets and the timeline display for |
| | 15 | hours on the tickets in the time period. |
| | 16 | |
| | 17 | - query filters are available to find hours for people, hours for |
| | 18 | tickets of a certain component, etc; |
| | 19 | |
| | 20 | - a view for {{{/hours/<ticket number>}}}; this displays the accrued hours |
| | 21 | for a particular ticket with a timeline-like view, but should also |
| | 22 | allow adding of new hours (by default, on "today", but this should |
| | 23 | be changeable via dropdown menus for day, month, year, etc), |
| | 24 | editing previously entered hours (amount, date, description) and |
| | 25 | deleting previously alloted hours |
| | 26 | |
| | 27 | - the view at {{{/hours/<ticket number>}}} by default only allows adding/editing |
| | 28 | of one's own hours on the ticket; however, if you are a |
| | 29 | TRAC_ADMIN, you should be able to add/edit/delete others' hours as well |
| | 30 | |
| | 31 | - the default query period is the last seven days |
| | 32 | |
| | 33 | * Hours are uniquely assigned to tickets and people (required fields) |
| | 34 | |
| | 35 | * hours may have a description, which should be displayed in the |
| | 36 | applicable views; if a description is provided, the hours and |
| | 37 | description are logged to ticket comments |
| | 38 | |
| | 39 | * ticket <number> has a link to {{{/hours/<number>}}} so that a user |
| | 40 | could add and view hours for the ticket |
| | 41 | |
| | 42 | Hour tracking and estimation is most useful when the following questions |
| | 43 | can be answered: |
| | 44 | |
| | 45 | * How much time has been spent on a project? |
| | 46 | |
| | 47 | * How much time remains in a budget (estimate for a project)? |
| | 48 | |
| | 49 | * How much time have we committed to for the next time period ? |
| | 50 | |
| | 51 | * How much time is a developer committed to over the next time period? |
| | 52 | |
| | 53 | If we put hour estimates on tickets, assign tickets to people, associate |
| | 54 | tickets with milestones, and give milestones due dates, a good time |
| | 55 | tracking plugin could generate reports to answer those questions. |
| | 56 | |
| | 57 | For other trac time-tracking solutions, see |
| | 58 | http://trac.edgewall.org/wiki/TimeTracking |
