ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Filter for integer custom field has options for searching text (Bug #387)

Added by Johan Levin at 2011-05-09 02:29 pm. Updated at 2011-07-04 09:58 pm.

Status:Duplicate Start date:2011-05-09
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Issue tracking
Target version:-
Remote issue URL: Affected version:1.3.0

Description

When using an integer custom field for filtering in the issues list then the search options are is, contains, is not and doesn't contain. That doesn't make much sense for an integer field. I think that e.g. <=, <, ==, =>, >, and != would be better options.

Steps to duplicate:
  1. Create a new custom field of type Integer and tick "Used as a filter"
  2. Enable it for a project
  3. Go to the project and click the "Issues" tab
  4. Choose the new field from the "Add filter" drop down.

The new filter will contain the same options you get for text fields (is, contains etc) and not options relevant for numbers.

(

Related issues

duplicates Bug #498: Wrong filters for int and float custom fields Closed 2011-06-30

History

#1
Updated by Johan Levin at 2011-05-10 07:30 am

Plus the search options "is null" and "is not null" (or some less technical wording) would be good when filtering on integer fields that aren't required.

#2
Updated by Felix Schäfer at 2011-07-04 09:58 pm

I just noticed I didn't search hard enough for already open bugs when I (re)-discovered this, sorry.

Marking this issue as duplicate as more discussion and fixing has already been done on the newer one.

  • Status changed from Open to Duplicate

Also available in: Atom PDF