Changes between Version 5 and Version 6 of TimeEstimationAndQuotingSpecification


Ignore:
Timestamp:
Nov 24, 2006 8:14:47 AM (8 years ago)
Author:
anonymous
Comment:

typo

Legend:

Unmodified
Added
Removed
Modified
  • TimeEstimationAndQuotingSpecification

    v5 v6  
    44 1. We wish to be able to note on a ticket the amount of time a developer spent on it.  This should be a list rather than a single box with total hours, because many developers may work on this ticket many times before the ticket is complete.  Currently we plan to add this to comments on a ticket. (Possibly as a separate table that references comments) 
    55 1. a ticket should show a summary of the time spent per developer and in total 
    6  1. a ticket should have the an estimated time field attached (probably just a custom field specified in trac.ini).   
     6 1. a ticket should have 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. 
    88 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)