Details

    • Type: Task
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Action/Notifier
    • Labels:
      None

      Description

      This is a follow-up to an e-mail discussion, just a reminder to review a behavior and decide if it is fine as-is or may need an update to semantics. The conversation:

      Jay: I noticed that the Calendar constraint always drives off the event ctime. Is that what you intended? My initial thought was that it would be applied to the lifecycle timestamp. I can see arguments for both approaches.

      Lucas: Originally it was intended. As several status can be defined, each one has its own time, but ctime is shared for all of them. so, if you filter with ACK and RESOLVED and a time, perhaps it needs to match each state with its own time. Which is not bad, it might have sense, I need to review original examples to see if such change would modify the intended behavior in what is tested now.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                rutlucas Lucas Ponce
                Reporter:
                jayshaughnessy Jay Shaughnessy
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: