Custom query fails when using custom ticket field has same name as existing ticket field

[rsivak@…]

Traceback (most recent call last):

  File "/usr/local/lib/python2.4/site-packages/trac/web/cgi_frontend.py", line 130, in run
    dispatch_request(req.path_info, req, env)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 139, in dispatch_request
    dispatcher.dispatch(req)
  File "/usr/local/lib/python2.4/site-packages/trac/web/main.py", line 107, in dispatch
    resp = chosen_handler.process_request(req)
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/query.py", line 414, in process_request
    self.display_html(req, query)
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/query.py", line 522, in display_html
    tickets = query.execute(db)
  File "/usr/local/lib/python2.4/site-packages/trac/ticket/query.py", line 157, in execute
    val = int(val)
ValueError: invalid literal for int(): 15m

probably has somethign to do with my custom field.

time = select
time.label=Time
time.options=|15|30|45|60|75|90|1h45m|2h|2h15m|2h30m|3h
time.value=0

the options were 15m|30m|45m, etc but I changed them in hopes the error would go away, but it hasn't.

[Christian Boos]

This has to do with the name of your custom field, which conflicts with one of the default field name for the tickets.

For now, as a workaround, simply choose another name for your custom field.

In order to close this issue, this limitation should either be documented or lifted…

[sid]

This is a duplicate of #1449.