Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3999

Timezone is applied wrong to bucketLimiting filter on group by date with unit

    XMLWordPrintable

    Details

    • Type: Bug Report
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: 3.1.0
    • Fix Version/s: 3.2.0, 3.2.0-alpha1, 3.2.0-alpha2
    • Component/s: backend
    • Labels:
      None
    • Epic Link:
    • Effort:
      Not defined

      Description

      Given:

      • I have engine data in a timezone less (e.g. UTC) than the one Optimize (Europe/Berlin) is in
      • Optimize imports the data
      • A groupBy date report with a selected unit (e.g. month) without any user-defined date filters.

      When:

      • The report gets evaluated in a timezone with an offset greater than the engine data (e.g. Europe/Berlin)

      Then:

      • The `filterLimitedAggregation` uses the wrong time zone for the to value, e.g. given a groupByStartDate report where the latest timestamp is `2020-04-15T20:56:41.003+0200`, then the following filter get's generated:
        "from": "1937-01-01T00:00:00.000+0100",
        "to": "2020-04-15T18:56:41.003+0200",
        

        and the entities within the time zone difference window are not part of the result

      Expected:
      The applied filter should catch the latest entities correctly

        mgm-controller-panel

        This is the controller panel for Smart Panels app

          Attachments

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Salesforce