Edgewall Software

Opened 11 years ago

Last modified 11 years ago

#10202 new defect

TracQuery fails to handle checkbox custom fields

Reported by: anonymous Owned by:
Priority: normal Milestone: next-major-releases
Component: query system Version: 0.12-stable
Severity: major Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:


Define a custom field

col_private = checkbox
col_private.label = Private
col_private.value = 0
col_private.order = 10

If you now create a new TracQuery via webpage, select this custom field for filter and set filter value to 'No', all previous created tickets are filtered out. Ok, accepting that the old tickets do not have a "Private" value set, we edit the query:-String and replace col_private=0 by col_private!=1. But now all tickets are listed, including all tickets set as "Private". The macro TicketQuery "fails" too using col_private=0 for filtering, but can handle col_private!=1 properly.

Trac 0.12.2
Babel 0.9.6
Genshi 0.6
pysqlite 2.6.3
Python 2.4.3 (#1, Sep 3 2009, 15:37:37) [GCC 4.1.2 20080704 (Red Hat 4.1.2-46)]
pytz 2011e
setuptools 0.6c11
SQLite 3.3.6
Subversion 1.4.2 (r22196)
jQuery: 1.4.2

Attachments (0)

Change History (1)

comment:1 by Remy Blank, 11 years ago

Milestone: next-major-0.1X

Thanks for the report. This doesn't surprise me, as we do have some other issues with newly-added custom fields. Unfortunately, it's not going to be easy to fix.

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
The ticket will be disowned.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.