Edgewall Software

Changes between Version 19 and Version 20 of TimeTracking


Ignore:
Timestamp:
Dec 5, 2005, 10:28:41 PM (18 years ago)
Author:
stp
Comment:

Removed error report, since this should be fixed in 0.9.2

Legend:

Unmodified
Added
Removed
Modified
  • TimeTracking

    v19 v20  
    148148
    149149This closes ticket #1, increases the time spent by 1 hour and decreases the remaining time by 1 hour.
    150 
    151 -----
    152 ==== [ticket:2442 Ticket #2442 (defect)] ====
    153 
    154 I tried adding the 0.9 mod today and hit a little static in the above. First, of course the .diff doesn't work for 0.9.1. Rolled back and followed steps above but the roadmap breaks with:
    155 
    156 {{{
    157 Traceback (most recent call last):
    158   File "/usr/lib/python2.3/site-packages/trac/web/cgi_frontend.py", line 131, in run
    159     dispatch_request(req.path_info, req, env)
    160   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 139, in dispatch_request
    161     dispatcher.dispatch(req)
    162   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 107, in dispatch
    163     resp = chosen_handler.process_request(req)
    164   File "/usr/lib/python2.3/site-packages/trac/ticket/roadmap.py", line 213, in process_request
    165     [ 'owner', 'tt_estimated', 'tt_remaining', 'tt_spent' ])
    166   File "/usr/lib/python2.3/site-packages/trac/ticket/roadmap.py", line 66, in get_tickets_for_milestone
    167     ticket = {
    168 TypeError: tuple indices must be integers
    169 }}}
    170 
    171 Using SQLite 3.2.7. I have not added estimates to every existing ticket ... would hope that's not necessary ... anyone else struck this?