Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 145811

Summary:	"Filter out" on Object References view adds filters that user didn't add
Product:	z_Archived	Reporter:	Ruth Lee <ruthdaly>
Component:	TPTP	Assignee:	Eugene Chan <ewchan>
Status:	CLOSED INVALID	QA Contact:
Severity:	major
Priority:	P1	CC:	jkubasta, nmehrega
Version:	unspecified	Keywords:	plan
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:	closed460

Description Ruth Lee

2006-06-07 13:27:39 EDT

As part of running Trace.UI.Object_Reference_Test7, I opened the "Filter out..." on the Object Reference view and added a package name filter & clicked OK. I opened the "Filter out..." dialog again only to see that a Class name filter had been added, and I didn't add it. Not sure where it came from.

Every time that I click "OK" on that dialog and then reopen the dialog, I see a new Class name filter that I didn't add.

Comment 1 Eugene Chan

2006-06-09 15:05:59 EDT

Hi Ruth,
'Filter out...' action applies on selection made in Object Reference view. The filter entry "Class name <> foo" is added for the selection(foo) in the Object Reference view upon 'Filter out...' action performed.

Comment 2 Eugene Chan

2006-06-09 15:10:25 EDT

Also filtering is only applicable to the first level elements of object reference tree view. 'Filter out' action in other level has no effect and no entry will be added to filter.

Comment 3 Valentina Popescu

2006-06-11 21:55:48 EDT

not critical for 4.2; moving to 4.2.1

Comment 4 Eugene Chan

2006-09-25 10:39:31 EDT

Targeting to post 4.3 release.

Comment 5 Eugene Chan

2007-01-31 18:35:18 EST

Target to future. Cannot be contained in 4.4 due to limitation of resource.

Comment 6 Eugene Chan

2007-01-31 23:33:34 EST

Move target back to 4.4. Trace defects are mistakenly targeted in bulk move.

Comment 7 Navid Mehregani

2007-02-09 10:22:02 EST

Eugene, I don't think this defect is valid.  As you mentioned above the filters are added based on the user's selection.  Shouldn't this defect be marked as INVALID?

Comment 8 Eugene Chan

2007-05-09 15:43:23 EDT

The behavior described in Comment #0 is correct behavior.

Retested on driver tptp.sdk-TPTP-4.4.0-200705080100

Comment 9 Paul Slauenwhite

2009-06-30 09:49:52 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.

Comment 10 Paul Slauenwhite

2009-06-30 09:52:25 EDT

As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this originator of this enhancement/defect has an inactive Bugzilla account and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.