| Summary: | Execution History Editor: Searching | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Joe Toomey <jptoomey> | ||||
| Component: | TPTP | Assignee: | Bianca Jiang <bjiang> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P1 | CC: | bjiang, fmcgrath, kdsiefke, slavescu, suttonja, who | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 103103, 132857 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Joe Toomey
Also allow searching on extended properties. Also allow extension point to register custom event types for searching (i.e. HTTP Request) When designing this feature please take a look at how the Log and Profiling views are providing this kind of support, let me know if you need any details. We have a common filtering (querying) model/engine and UI (which also works for database backed resources). I plan to refactor the search mechanism to have better performance when used on database backed resources, I'll be interested to discuss this refactoring also in the context of Test model. Deferring from 4.1 as per the official 4.1 enhancement plan. http://eclipse.org/tptp/home/project_info/featureplans/features.php?source=All&project=All&release=4.1&file=TPTPFeatures_4.1.xml Updating priority to P1 (requesting for TPTP 4.2) Changed Version from future to 4.2 for inclusion in TPTP 4.2 release planning. Reassigning to Biance per her request. Also set Target to 4.2. proposed to be plan for 4.2 (plan keyword added) Target set to 4.2 Created attachment 36038 [details]
UI design doc.
UI prototyping done. sizing = 3 weeks. Delivered. ACTION: Please verify/close this defect. Closing by default since not closed by the originator in the 7+ months since being resolved. Please reopen if the issue is still present in the latest TPTP release or the resolution is not correct. |