Instance level filters should take reportType into account

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: backend
    • Not defined

      Context:

      While implementing OPT-4667, we noticed that currently some instance level filters which should take flowNode type into account do not do so. 
      For example, flowNode status filters should, when applied to userTask reports, only apply this status filter to flownodes of type userTask. Otherwise, instances may still be included in the result when another flowNode matches the filter even though no userTasks do so: for example, an instance with a completed startEvent but no completed UserTasks will still be included in a userTask report with completedFlowNodesOnly filter.

      As far as I can see this is required for flowNode status and duration filters, but lets also evaluate if this needs to be taken into account for any other filter type. IdentityFilters already take the reportType into account, we can use similar logic for the other flownode filters.

      AT:

      • evaluate which instance level filters should take reportType into account and adjust accordingly

       

            Assignee:
            Unassigned
            Reporter:
            Helene Waechtler
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: