I'm forced to use defined filter variables when filter property is identical

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Fixed
    • Priority: L3 - Default
    • 7.11.0
    • Affects Version/s: 7.11.0-alpha3
    • Component/s: tasklist
    • None

      // Given

      • Tasklist filter with invoiceNumber : Invoice Number as defined Variable
      • Process instance with user task and process variable called number

      // When
      I filter for tasks by process variable and enter number as filter property

      // Then
      the filter automatically uses invoiceNumber as filter property

      // Expected Behavior
      I can ignore the proposed variable name and use number as filter property

            Assignee:
            Unassigned
            Reporter:
            Michael Schoettes
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: