View Issue Details

IDProjectCategoryView StatusLast Update
0007007mantisbtfilterspublic2017-08-08 03:51
Reportergce Assigned Toatrol  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version1.0.2 
Summary0007007: Filter for custom field is lacking [empty]
Description

I have a custom field with the following properties:
Type: String
Min. Length: 0
Max. Length: 1

In some issues it has no value (i.e. it is empty) and in other issues it has one of the values "A", "B", "C".

In "View issues", where I can set the filter criteria, also my custom field appears
and I can select one (or in advanced filter mode even more) of the following values:
[any] ... my custom field is no filter criterion
[none] ... NO issue passes the filter (does this make sense?)
A ... only issues, where my custom field has the value "A", pass the filter
B ... only issues, where my custom field has the value "B", pass the filter
C ... only issues, where my custom field has the value "C", pass the filter

But there is no possibility to express, that only issues, where my custom field has no value (i.e. it is empty), shall pass the filter.

TagsNo tags attached.

Relationships

related to 0023160 closedcproensa [Feature request] Option to filter custom text fields based on being non-blank 

Activities

gce

gce

2006-04-29 12:10

reporter   ~0012754

In order to provide the possibility to express, that only issues, where the custom field has no value (i.e. it is empty), shall pass the filter,

  • either an additional filter value [empty] (or just an empty value) should be provided
  • or the value "[none]" (which IMO does not make sense currently) could get this new meaning.
jasonrumney

jasonrumney

2017-07-28 02:40

reporter   ~0057352

In 1.3.11 [none] seems to work as expected here, and I think it was working in 1.2.x as well, so I guess this bug should be closed.

atrol

atrol

2017-07-28 04:05

developer   ~0057353

Last edited: 2017-07-28 04:06

Thanks @jasonrumney for the note.
You are right, it's fixed since 1.2

This issue was reported against an old version of MantisBT which is no longer supported.
The issue is no longer reproducible on latest stable version [1]

[1] http://www.mantisbt.org/download.php