Refactor Report Updating

XMLWordPrintable

    • Type: Task
    • Resolution: Fixed
    • Priority: L3 - Default
    • 2.4.0-alpha1, 2.4.0
    • Affects Version/s: None
    • Component/s: frontend
    • None

      Report updating is a mess that should be untangled. Changes to the report and its configuration is done in so many different places that it's almost impossible to keep track of and very easy to introduce bugs.

      Basis for a refactoring should be these two functions

        1.
        		 Reset to default for combined bar charts with multiple reports crashes Bug Part Done Unassigned
        2.
        		 Use $set semantic in nested Configuration options Sub-task Done Unassigned
        3.
        		 Create configuration fields on report creation Sub-task Done Unassigned
        4.
        		 ProcessParts should use $set mechanix to add itself to parameters instead of overwriting it Sub-task Done Unassigned
        5.
        		 Use central update handler and pass report to process definition selection Sub-task Done Unassigned
        6.
        		 Get rid of updateConfiguration method Sub-task Done Unassigned
        7.
        		 Fix tests Sub-task Done Unassigned
        8.
        		 Write new tests Sub-task Done Unassigned
        9.
        		 Make sure to update configuration when combined report is updated transitively Sub-task Done Unassigned
        10.
        		 Make the Chart component use new targetValue structure Sub-task Done Unassigned
        11.
        		 setting process part makes view grey in views that are not process instance duration Bug Part Done Unassigned
        12.
        		 Analysis Filter broken Bug Part Done Unassigned
        13.
        		 Reordering tables in combined report does not change report visualization Bug Part Done Unassigned
        14.
        		 use distinct update methods for view, groupby and visualization Sub-task Done Unassigned

            Assignee:
            Unassigned
            Reporter:
            Sebastian Stamm
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: