Changes between Version 28 and Version 29 of TracHoursPlugin


Ignore:
Timestamp:
Nov 6, 2009, 7:47:03 PM (5 years ago)
Author:
k0s
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracHoursPlugin

    v28 v29  
    88== Goals of TracHoursPlugin ==
    99
    10 TracHoursPlugin is done in response to
    11 [http://trac-hacks.org/wiki/TimingAndEstimationPlugin TimingAndEstimationPlugin], but tailored to suit present needs:
     10TracHoursPlugin is an alternative
     11[http://trac-hacks.org/wiki/TimingAndEstimationPlugin TimingAndEstimationPlugin], but with a different approach:
    1212
    13  * Instead of adding hours via the comment system, there is a separate view for hours:
    14    - `/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.
    15    - query filters are available to find hours for people, hours for tickets of a certain component, etc;
    16    - 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
    17    - 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
    18 
    19  * hours are uniquely assigned to tickets and people (required fields)
    20 
     13 * instead of adding hours only via ticket fields, there is a separate view for managing ticket hours. `/hours/<ticket number>` 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 if you have the appropriate permissions (`TICKET_ADD_HOURS` for your own hours, `TRAC_ADMIN` for the hours of others).   
     14 * a management and query view is at `/hours`.  This view displays the hours for all tickets for a given time period (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.   
     15 * hours are uniquely assigned to tickets and people
    2116 * 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
    22 
    23  * `/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
     17 * Tickets have links to `/hours/<ticket number>` as the total hours field so that a user can add and view hours for the ticket
    2418
    2519Hour tracking and estimation is most useful when the following questions can be answered:
     
    3125
    3226If we put hour estimates on tickets, assign tickets to people, associate
    33 tickets with milestones, and give milestones due dates, a good time
    34 tracking plugin could generate reports to answer those questions.
     27tickets with milestones, and give milestones due dates, !TracHours can generate reports to answer those questions.
    3528
    3629For other trac time-tracking solutions, see