• Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.4.0.Final
    • None
    • None
    • None
    • None

      As a windup user
      I want be able to export the analysis data / results from my analyzed applications
      So I can perform my own custom reports / tracking / post-analysis.
      Validation criteria:
      Data is exported by row, in the format of:
      Rule Id, (Problem type - Classification vs. Hint), Title, Description, Links, Application, File Name, File Path, Line, Story points
      Columns are delimited by a unique character
      Delimiter characters in the data are escaped to prevent import defects
      Data is importable by Excel, LibreOffice and spreadsheet tools
      Export is performed on demand (enabled by configuration parameter --export)
      Export is outputted to the report directory and is called application_name.export
      Export is disabled by default
      Tasks:
      Create export configuration parameter
      Add a CSV/export library to the reporting add-on
      Create a RuleProvider to run during report rendering phase that gathers data from the graph and writes the export file.
      Research how to handle delimiter escaping in specified spreadsheet tools
      mockMost tools have a dialog like this http://bit.ly/1UAMrTP
      Transpose/cleanse the data to handle delimiter characters
      Write test cases
      Delimiter escaping
      Configuration parameter actually creates report
      Export is disabled by default
      Create documentation about the feature and how to import into a spreadsheet tool
      Points: 21, 34 (marek), 8 (jess), 13, 13, 21, 21 = 21
      Impediments:
      Milestones: Reporting
      Architectural impact:
      Comments: Marek thinks there will be performance implications and lots of corner cases to test.

              mbriskar_jira Matej Briskar (Inactive)
              mbriskar_jira Matej Briskar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: