Traceback (most recent call last):

[anonymous]

Python Traceback

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 406, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/trac/web/main.py", line 237, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev-py2.4.egg/webadmin/web_ui.py", line 119, in process_request
    path_info)
  File "/usr/lib/python2.4/site-packages/TracWebAdmin-0.1.2dev-py2.4.egg/webadmin/ticket.py", line 163, in process_admin_request
    mil.due = util.parse_date(req.args.get('duedate'))
  File "/usr/lib/python2.4/site-packages/trac/util/datefmt.py", line 114, in parse_date
    raise ValueError, '%s is not a known date format.' % text
ValueError: 081308 is not a known date format.

[osimons]

If you had searched for 'ValueError parse_date' or similar, you'd have noticed a number of pre-existing tickets… You seem to be running an older version of Trac as this has been fixed for 0.11 - see #4927.

[Emmanuel Blot]

… or you did not used the format that is specified as a hint along with the date field.

Please also take care of defining a meaningful ticket summary when you report an issue, as specified in the NewTicketGuidelines, quoting: Provide a concise and precise Summary. As when you write an e-mail, the ticket's summary is the first thing people will see about this ticket, in the timeline, reports and other places in Trac, so it's quite important to get it right.