Defect #7596
closed
Can't filter custom fields based on blank or non-blank values
Added by Kioma Aldecoa about 13 years ago.
Updated almost 13 years ago.
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.
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.
- 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.
- 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".
Is your custom field a mandatory field ?
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.
Hear, hear! I would really like to see this as capability as well -- have been unable to figure out a good workaround.
- Status changed from Reopened to Closed
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by