Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-47952

Browser back behaviour for result screen is broken

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: blueocean-plugin
    • Labels:
      None
    • Environment:
      ci.jenkins.io
      BO 1.31 on Jenkins 2.73.3
    • Epic Link:
    • Sprint:
      Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 5, Blue Ocean 1.5 - beta 1
    • Similar Issues:

      Description

      Steps to reproduce

      1. Open https://ci.jenkins.io/blue/organizations/jenkins/Core%2Fjenkins/detail/PR-3082/8/pipeline/ in a new window or tab
      2. Click "Artifacts"
      3. Press Escape
      4. Press Back

      Expected result 1: Artifacts view of build
      Actual result 1: Pipeline view of build


      Further steps:

      1. Click "Artifacts"
      2. Press Escape

      Expected result 2: Artifacts view of build; back button available.

      Actual result 2: Activity view of project, but has Pipeline view URL; back button disabled.

        Attachments

          Issue Links

            Activity

            Hide
            kshultz Karl Shultz added a comment -

            Testing Notes

            • Any final implementation of this should include ATH test(s) which validate that the browser's Back button produces the expected result.
            • This could be created as its own test case (probably in the "offline" set of tests), and/or the use of browser button navigation could be included in existing cases.
            • Correct behavior of browser buttons probably warrants its own ticket or tickets. I'll look for one, and if there's not one there, I'll create it.
            Show
            kshultz Karl Shultz added a comment - Testing Notes Any final implementation of this should include ATH test(s) which validate that the browser's Back button produces the expected result. This could be created as its own test case (probably in the "offline" set of tests), and/or the use of browser button navigation could be included in existing cases. Correct behavior of browser buttons probably warrants its own ticket or tickets. I'll look for one, and if there's not one there, I'll create it.

              People

              • Assignee:
                nicu Nicolae Pascu
                Reporter:
                danielbeck Daniel Beck
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: