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

Task List: OrQueries doesn't behave as aspected - properties exclude each others

    Details

    • Type: Bug Report
    • Status: Open
    • Priority: L3 - Default
    • Resolution: Unresolved
    • Affects Version/s: 7.9.0
    • Fix Version/s: None
    • Component/s: tasklist
    • Labels:
      None
    • Title Keywords:
      orqueries assignee involvedUser task list

      Description

      I'm getting an weird behaviour using OrQueries:

      Case 1 - filtering Involved user 1:

      { "involvedUser": 1, "active": true }

      Result is a empty array:
      []

      Case 2: Filtering by assignee 1

      { "assignee": "1", "active": true }

      I get a response with 16 tasks.

      Now, using orQueries:
      {
      "orQueries":[

      { "involvedUser": 1, "assignee": "1" }

      ],
      "active": true
      }
      My result consists in only one task.

      It should be the 16, since its an Or operation.

      BTW, using OrQueries with only one filter behave as expected:
      {
      "orQueries":[

      { "assignee": "1" }

      ],
      "active": true
      }
      Returns the 16 taks.

      I'm using Camunda 7.9

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            inflorTec Vagner Gon Furtado
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development