Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-1961

ConversationEntry.isCurrent returns incorrect value when the ConversationEntry represents a temporary conversation

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Optional
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None

      Description

      ConversationEntry.isCurrent always returns false for the CE that represents the current conversaion if that conversation is not long running.

      This was discovered when attempting to to work around JBSEAM-1901.

      I would expect the CE to return true if it represents the current conversation reguarless of the longRunning/temporary state of the conversation.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                cmrudd Chris Rudd
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: