Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-80904

Context panels (replacing glance panels) do not correctly reload the iframe when using the back button or switching between tickets in backlogs

    XMLWordPrintable

Details

    Description

      Issue Summary

      This is reproducible on Data Center: (no)

      Steps to Reproduce

      (In Issue view)

      1. With Tempo installed, have a issue with subtasks or children. It helps to have different time logged on each to see what’s happening
      1. Go to the issue view and open the Tempo context panel. Take note of the data
      1. Open the subtask/child and take note how both the main view and sidebar change correctly
      1. Use the Browser back button to go back to the parent issue

      (In backlog)

      • With Tempo installed, have at least two issues. It helps to have different time logged on each to see what’s happening
      • Go to a backlog view and click on an issue to open the sidebar. Have the Tempo context panel open. Take note of the data
      • Switch to another issue by clicking it, so that it opens in the sidebar and take note how both the main plugin panel and context panel data change correctly
      • Go back to the first issue by clicking it

      Expected Results

      (In Issue view)

      The sidebar iframe is reloaded like it used to with glance panels and is still done in the main view

      (In backlog)

      The context panel iframe is reloaded

      Actual Results

      (In Issue view)

      • The sidebar plugin iframe does not get reloaded for the correct ticket and thus the data from the child/subtask is still displayed
      • The main view on the left is reloaded, including the Tempo iframe.

      (In backlog)

      • The context panel plugin iframe does not get reloaded for the correct ticket and thus the data from the second issue is still displayed
      • The main plugin panel is reloaded and shows correct data

       

      Additional Information

      The problem also occurs when loading an issue from a board.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        1. backlog.mov
          5.87 MB
        2. issueview.mov
          5.39 MB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              e555ca5e1233 Bartosz Robakowski
              Votes:
              8 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: