[#CHD-1168] [Custom Fields] Multi chooser searches for "not in list" do not exclude matches - WebGroup Media LLC

Issue Details [XML]

Key:	CHD-1168
Type:	Bug
Status:	Open
Assignee:	Unassigned
Reporter:	Joe Geck
Votes:	1
Watchers:	1

Operations

Clone this issue

If you were logged in you would be able to see more operations.

Cerberus Helpdesk

[Custom Fields] Multi chooser searches for "not in list" do not exclude matches

Created: 03/Apr/09 08:59 PM Updated: 01/Aug/09 09:09 PM

Fix Version/s:

Sea of 1000 Wishes

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

File Attachments:

None

Image Attachments:

1. multi-picklist_search_results.jpg
(95 kb)

Value:	2 - Significant Value
Marquee:	Custom Fields

Description

Summary:
This ones probably best explained with a picture so see the attached screenshot. But the basic idea is that "mutli" choosers such as multi-picklist and multi-checkbox handle "not in list" searches differently than expected. If you have say a ticket with multi-picklist 'Option A' chosen and then do a search for "not in list" = 'Option A', that ticket will still appear in the worklist.

Steps [based on screenshot]:
1) Create a new multi-picklist custom field for 'addresses' via 'helpdesk setup', e.g.

Source: Address
Type: "Pick a fruit"
Options:
Apple
Banana
Orange

2) Click over to 'address book', 'addresses' tab and check to make sure you have a couple of addresses to play with.
3) Click 'customize' to expose the multi-picklist "Pick a fruit".
4) Using 'bulk update' and '(peek)' set one of your addresses to "Banana" and the rest to "Apple".
5) Add a search filter where:

"Pick a fruit" not in list 'Apple'

Result:
Observe that all of your addresses are returned even the ones where 'Apple' was set.

Note:
This applies to all Helpdesk objects too, tickets, addresses, time tracking entries, etc.

All

Comments

Work Log

Change History

Sort Order:

Comment by Joe Geck [03/Apr/09 09:05 PM]

[ Permlink ]

Attached screenshot (multi-picklist_search_results).

Comment by Jeff Standen [WGM] [18/May/09 10:22 PM]

[ Permlink ]

Yeah, this will be a little tricky on the multi-value fields. Right now if there are 4 values set, the query can discard 1 (NOT IN) and there are still 3 hits. This would be simpler to fix as a single query, but it's a bit tougher in the abstract guts of Devblocks DAO. I'll background this in my head and come back later w/ a solution.