0017810: Filtering by custom field value "none" also returns issues not linked with that custom field

ID	Project	Category	View Status	Date Submitted	Last Update
0017810	mantisbt	filters	public	2014-10-28 07:14	2017-08-16 13:56

Reporter	mt_s01	Assigned To	cproensa
Priority	high	Severity	major	Reproducibility	always
Status	acknowledged	Resolution	open
Platform	LINUX	OS	CENTOS	OS Version	6.5
Product Version	1.2.15

Summary	0017810: Filtering by custom field value "none" also returns issues not linked with that custom field
Description	filters and custom field by project Postby mt_s01 » Sep 25, 2014 10:46 am Hello, From the "All bugs" page, I use the filter with several custom fields which belong to different projects. For example, I have the custom field "custom_field_1" linked to "PROJECT 1". When I set the filter on the "custom_field_1" at "none", MANTIS displays all bugs from PROJECT A where "custom_field_1" is null but it displays all bug from PROJECT B where the custom field is not present too. Is this a bug ? Thanks for help.
Steps To Reproduce	1) Crete project1 and project2 2) Create a custom field cp1 specific to project1 Display it in filter. 3) View all bugs page 4) Set custom field cp1 to none 5) It displays all bugs even bugs of project2 where the field is not define.
Tags	No tags attached.

cproensa 2017-08-16 13:42 reporter ~0057480	The filter system is considering an issue that does not have the custom field linked (by the field configuration for linked projects), is matching the condition of "field value = none". I'm not sure this is a bug, as that issue does effectively not have any value for the queried custom field. However, it's also true that it doesn't have the possibility to have any value, so if you search for issues with a value of "none", you may actually want to get only issues that have that field linked. I'd like to hear other team opinions on this.

cproensa 2017-08-16 13:56 reporter ~0057481	I have updated the summary to better explain the issue