Details

    • Type: Sub-task
    • Status: Done
    • Priority: L3 - Default
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.7.0
    • Component/s: backend
    • Labels:
      None

      Description

      At the moment, the state of a trace doesn't take into account the valid repetition of an event - meaning that models with loops won't be fairly reflected in either trace or sequences. This will have an impact on our suggestions, as well as the counts of sequences (which will most likely be used for event counts in future).

      ATs:

      • Event traces and sequences support the valid repetition of events. Events should only be considered modifications if the event ID and group/source/eventName are all the same

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            joshua.windels Joshua Windels
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: