Changes between Version 2 and Version 3 of TracHoursPlugin

Aug 7, 2008, 6:13:03 PM (10 years ago)
Jeff Hammel

bah! include macro fails me; just pasting the text


  • TracHoursPlugin

    v2 v3  
    11= keep track of hours spent on tickets =
    3 [[Include(]]
     3== TracHoursPlugin ==
     5The goal of this plugin is to help keep trac of hours worked on
     6tickets.  This is done in response to
     7TimingAndEstimationPlugin, but tailored to suit present needs:
     9 * Instead of adding hours via the comment system, there is a separate
     10  view for hours:
     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.
     17  - query filters are available to find hours for people, hours for
     18   tickets of a certain component, etc;
     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
     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
     31 - the default query period is the last seven days
     33 * Hours are uniquely assigned to tickets and people (required fields)
     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
     39 * ticket <number> has a link to {{{/hours/<number>}}} so that a user
     40  could add and view hours for the ticket
     42Hour tracking and estimation is most useful when the following questions
     43 can be answered:
     45 * How much time has been spent on a project?
     47 * How much time remains in a budget (estimate for a project)?
     49 * How much time have we committed to for the next time period ?
     51 * How much time is a developer committed to over the next time period?
     53If we put hour estimates on tickets, assign tickets to people, associate
     54tickets with milestones, and give milestones due dates, a good time
     55tracking plugin could generate reports to answer those questions.
     57For other trac time-tracking solutions, see
    560== Bugs/Feature Requests ==
     62Please note all features at
    764== Download ==