Unsaved Report Evaluation fails with Z-Offset last modified timestamp

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 3.3.0
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      Given:
      The users local timezone is `Europe/London` ot GMT.

      When:
      The user creates a report

      Then:
      the report evaluation fails and "no data is shown", in the console an error on the evaluation call is shown relating to the lastModified data format

      Expected:
      although the UK left the EU, report evaluation should still work for people from there

      Context:
      Unsaved report evaluation currently fails with Z-Offset last modified data. The deserialization fails as it does not match our date time format. We should handle this case in the BE as the FE currently passes the Z-Offset format rather than the extended +0000

            Assignee:
            Unassigned
            Reporter:
            Joshua Windels
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: