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: backend
    • Labels:
      None

      Description

      Currently, the backend responds with a 500 error code when trying to evaluate a report that has no visualization set. Since the backend does not care about the visualization, it should still evaluate the report and send the result to the frontend.

      This allows us to fetch data earlier so that we can get rid of a loading delay when the user ultimately selects a visualization. It also allows us to assume that a change in the visualization never needs a re-evaluation of the report, making report updating easier

        Issue Links

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: