Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8071

Filter for due date and follow up date is not applied correctly in case of OR query

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.8.0, 7.8.0-alpha3
    • 7.8.0-alpha2
    • engine
    • None

    Description

      Steps to reproduce:

      I have following user tasks:

      • tasks with due date set to today + 7 days
      • tasks without due date

      When I create a filter with ALL instruction and with one criteria "Due After today + 8 days" -> I get empty result (CORRECT)
      When I create a filter with ANY instruction and with the same single criteria -> I get the list of tasks for which due date is not null (WRONG)

      These are the JSON payloads for filter creation:

      {
        "id": "9703f13b-71fa-11e7-9974-0a0027000006",
        "name": "Or test",
        "resourceType": "Task",
        "query": {
          "dueAfter": "2017-08-05T10:00:00.000+0200"
        },
        "properties": {
          "priority": 0,
          "color": "#555555",
          "refresh": false,
          "showUndefinedVariable": false
        }
      }
      

      and

      {
        "id": "9703f13b-71fa-11e7-9974-0a0027000006",
        "name": "Or test",
        "resourceType": "Task",
        "query": {
          "orQueries": [
            {
              "dueAfter": "2017-08-05T10:00:00.000+0200"
            }
          ]
        },
        "properties": {
          "priority": 0,
          "color": "#555555",
          "refresh": false,
          "showUndefinedVariable": false
        }
      }
      

      Expected behavior:
      The filter must be applied correctly and both filters must return the same result (empty list in this case).

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Activity

            People

              svetlana.dorokhova Svetlana Dorokhova
              svetlana.dorokhova Svetlana Dorokhova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce