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

Task Filter displays result that does not match to the filter query

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • tasklist
    • None

      Run the invoice show case. One instance is waiting at the review invoice task. One instance is waiting at the approve invoice task

      Reproduce:

      • Create a new filter with the following criteria:
        Key: Task name Value: review invoice
      • Create a new filter in the list of tasks:
        Type: Name Operator: = Value: approve invoice

      Problem:
      Approve Invoice Task is displayed in the list of tasks

      Expected behavior:
      List of tasks is empty

        This is the controller panel for Smart Panels app

            [CAM-6419] Task Filter displays result that does not match to the filter query

            Michael Schoettes created issue -
            Daniel Meyer made changes -
            Assignee New: Mariusz [ mariusz.sielski ]
            Daniel Meyer made changes -
            Rank New: Ranked higher
            Mariusz made changes -
            Assignee Original: Mariusz [ mariusz.sielski ] New: Johannes [ johannes.heinemann ]
            Johannes made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]

            Johannes added a comment - - edited

            The described problem in this issue is expected behavior: Task name and Name are both mapping to the same field in the engine logic. Therefore, by setting both filter criteria the Name filter is overwriting the Task name filter. A possibly desired behavior would be to refine the filter behavior, so both criteria would apply. However, such a refinement is not possible in the current Camunda engine.

            As a consequence, I close this issue unfixed. If you have questions related to this matter, don't hesitate to ask me.

            Johannes added a comment - - edited The described problem in this issue is expected behavior: Task name and Name are both mapping to the same field in the engine logic. Therefore, by setting both filter criteria the Name filter is overwriting the Task name filter. A possibly desired behavior would be to refine the filter behavior, so both criteria would apply. However, such a refinement is not possible in the current Camunda engine. As a consequence, I close this issue unfixed. If you have questions related to this matter, don't hesitate to ask me.
            Johannes made changes -
            Fix Version/s Original: 7.6.0 [ 14490 ]
            Johannes made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Thorben Lindhauer made changes -
            Workflow Original: camunda BPM [ 39220 ] New: Backup_camunda BPM [ 61919 ]

              johannes.heinemann Johannes
              michael.schoettes Michael Schoettes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: