Changes between Version 1 and Version 2 of TimeEstimationAndQuotingSpecification


Ignore:
Timestamp:
Jun 30, 2006, 7:21:22 PM (8 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TimeEstimationAndQuotingSpecification

    v1 v2  
    66 1. a ticket should have the an estimated time field attached (probably just a custom field specified in trac.ini). 
    77 1. Tickets should also provide a rate or fixed cost bounty field so that there is a corresponding price for the estimated time.
    8  1. We wish to be able to query per ticket / component / milestone / project (trac instance) how much time has been spent per developer and in total.
     8 1. We wish to be able to query per ticket / component / milestone / project (trac instance) how much time has been spent per developer and in total.  We should also be able to query this for different time periods (how much time this month did we spend on ticket 1)
    99 1. we should be able to query the amount over/under our estimation we were per per ticket / component / milestone / project (trac instance)
    1010 1. A permissions set that is associated with viewing and  adding/editing these fields
     
    1212
    1313== Specification ==
     14
    1415=== Time Tracking ===
     16In order to track how much time each developer is spending on a ticket, there should be some easy, queryable way to add time spent to a ticket.  My first thought on this is to add two fields next to the comment that are time spent (in hours) and whether or not this is billable time (a checkbox).  Then the developer (name) associated with that comment is also associated with the time. When a comment is added it should also add that time to the time log and update the total time spent for this ticket (which should probably be displayed in ticket properties as three fields, billable nonbillable, total) or a new time management section.  When displaying comments, where it currently displays "date time changed by user" we should append a time spent. 
     17
     18If there is an error in a reported time, the plugin should allow the user to enter a second comment with a negative time.  This will allow us to have a record of both the positive allotment of time as well as the redaction of that time.
     19
    1520=== Time Estimation and Price Quoting Facilities ===
    1621=== Querying New Info ===