Defect #7596

Can't filter custom fields based on blank or non-blank values

Added by Kioma Aldecoa over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:2011-02-10
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:Invalid Affected version:

Description

I have custom fields set up for projects. In the issue list, I'd like to be able to show only issues that have non-blank values present for the custom field. Currently (we have redmine 1.0.1) when attempting filter based on the "is not" criteria and a blank value, redmine comes back with an error that the field cannot be blank. Instead I would expect it to show issues where the value of that field is not blank.

History

#1 Updated by Mark Price over 9 years ago

Seeing the same issue in Redmine 1.1.1. I tried to work around this by setting a default value in the field that we would never use, and then use the "is not" default value. However it matches on all the existing bugs that were created before the default value was added.

#2 Updated by Jean-Philippe Lang over 9 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

Do not use the "is not" filter, use the "none" filter instead. It will list all issues that don't a value set for the custom field.

#3 Updated by Phil Manser over 9 years ago

  • Status changed from Closed to Reopened

Where do you see the "none" filter? I have a custom integer field and the only options I see are "is", "contains", "is not", and "doesn't contain". All of them expect a value. There is no "none" or "is not none".

#4 Updated by Etienne Massip over 9 years ago

Is your custom field a mandatory field ?

#5 Updated by Phil Manser over 9 years ago

Etienne Massip wrote:

Is your custom field a mandatory field ?

Nope, it's an optional field. Though I did try changing it to required and then back to optional hoping that that might make a new set of options show up, but to no avail.

#6 Updated by Ben Flaumenhaft over 9 years ago

Hear, hear! I would really like to see this as capability as well -- have been unable to figure out a good workaround.

#7 Updated by Etienne Massip over 9 years ago

  • Status changed from Reopened to Closed

It has been fixed by JPL with #6180 for 1.3.0.

Also available in: Atom PDF