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

nested conversations, redirects and refresh button

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 1.1.0.BETA2
    • Fix Version/s: 1.1.0.CR1
    • Component/s: Core
    • Labels:
      None

      Description

      Currently the nested conversation id goes into the URL, so there is no way to get the outer conversation id when the user presses refresh (we should put both in the URL and try one, then the other).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                gavin.king Gavin King
                Reporter:
                gavin.king Gavin King
              • Votes:
                2 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: