Details

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

      Description

      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

        Issue Links

          Activity

          Hide
          johannes.heinemann Johannes Heinemann added a comment -

          Also think about how to deal with changes in the configuration field in case the user performs a migration of Optimize to a new version.

          Show
          johannes.heinemann Johannes Heinemann added a comment - Also think about how to deal with changes in the configuration field in case the user performs a migration of Optimize to a new version.
          Hide
          sebastian.stamm Sebastian Stamm added a comment -

          There should not be any new code to review here, but you can still have a look whether we missed anything related to the report updating that we should refactor before considering this ticket done.

          Show
          sebastian.stamm Sebastian Stamm added a comment - There should not be any new code to review here, but you can still have a look whether we missed anything related to the report updating that we should refactor before considering this ticket done.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: