Community
Participate
Working Groups
Provide the capability to export symptoms from the UI into an XML file
Christine, Can you give more information about the feature request. there is current support to export symptom database to xml file from File->Export already.
It sounds like it's for individual symptoms. I'm guessing this is for moving symptoms around from database to database? Perhaps drag & drop and cut/copy/paste would be better..
This feature depends of 79235.
There is no need to export the symptom list into XML for consumption in our tool, we just need to save the resource with the container of the analysis result and surface that resource in Log Navigator. The Export capability in the Analysis Result view (which I suppose is this defect for) should be based on the infrastructure from 79235.
Yes, this is exporting some subset of the symptoms that result in the view after running analysis, like we have for exporting selected CBE into XML file. It has nothing to do with the symptom database itself. It is based on a previous request to export the analysis results into XML.
More detail on this: Provide the capability to export the symptom results into the an XML file based on the Symptom XML format which also includes the associated CBEs. All of the pertinent information like RecommendedActions and SymptomInformation, Rules should also be saved.
retarget to 4.2
update priority per Chris's request
Setting target to future so it doesn't show up in the 4.2 feature query.
*** This bug has been marked as a duplicate of bug 134828 ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As such, TPTP is not delivering enhancements. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement is resolved as WONTFIX. For this enhancement to be considered, please re-open with an attached patch including the Description Document (see http://www.eclipse.org/tptp/home/documents/process/development/description_documents.html), code (see http://www.eclipse.org/tptp/home/documents/resources/TPTPDevGuide.htm), and test cases (see http://www.eclipse.org/tptp/home/documents/process/TPTP_Testing_Strategy.html).
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 enhancement/defect has been resolved and unverified for more than 1 year 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.
