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

Pipeline config "cog" to link to classic config screen

    XMLWordPrintable

    Details

    • Similar Issues:
    • Epic Link:
    • Sprint:
      arctic

      Description

      Increasingly there have been demands to have a link to equivalent classic pages, specifically around config. There are designs for this that use a "cog" icon.

      These can link to the config screen in classic until there is an equivalent config screen for blue ocean.

      In scope:

      • Add a cog to pipeline results screen that links to config screen of classic
      • Add a cog to pipeline summary screen in the case of multibranch linking to classic
      • In the case of a github organization created job, the cog should link to the config for the org in classic (which is the only real config page)
      • Cog should open config screen in new browser tab

      When clicking on the cog, for example on the multibranch project called "keitha", it should link to something like this:

      (the uri pattern is predictable, so should be easy).

        Attachments

          Activity

          michaelneale Michael Neale created issue -
          michaelneale Michael Neale made changes -
          Field Original Value New Value
          Epic Link JENKINS-35761 [ 171656 ]
          michaelneale Michael Neale made changes -
          Labels adoption
          michaelneale Michael Neale made changes -
          Sprint arctic [ 131 ]
          michaelneale Michael Neale made changes -
          michaelneale Michael Neale made changes -
          Description Increasingly there have been demands to have a link to equivalent classic pages, specifically around config. There are designs for this that use a "cog" icon.

          These can link to the config screen in classic until there is an equivalent config screen for blue ocean.

          In scope:
          * Add a cog to pipeline results screen that links to config screen of classic
          * Add a cog to pipeline summary screen in the case of multibranch linking to classic
          * In the case of a github organization created job, the cog should link to the config for the org in classic (which is the only real config page)

           !Screen Shot 2016-10-28 at 1.19.05 pm.png|thumbnail! !Screen Shot 2016-10-28 at 1.19.24 pm.png|thumbnail!
          Increasingly there have been demands to have a link to equivalent classic pages, specifically around config. There are designs for this that use a "cog" icon.

          These can link to the config screen in classic until there is an equivalent config screen for blue ocean.

          In scope:
          * Add a cog to pipeline results screen that links to config screen of classic
          * Add a cog to pipeline summary screen in the case of multibranch linking to classic
          * In the case of a github organization created job, the cog should link to the config for the org in classic (which is the only real config page)

           !Screen Shot 2016-10-28 at 1.19.05 pm.png|thumbnail! !Screen Shot 2016-10-28 at 1.19.24 pm.png|thumbnail!


          When clicking on the cog, for example on the multibranch project called "keitha", it should link to something like this:

           !Screen Shot 2016-10-31 at 9.52.58 am.png|thumbnail!

          (the uri pattern is predictable, so should be easy).
          michaelneale Michael Neale made changes -
          Description Increasingly there have been demands to have a link to equivalent classic pages, specifically around config. There are designs for this that use a "cog" icon.

          These can link to the config screen in classic until there is an equivalent config screen for blue ocean.

          In scope:
          * Add a cog to pipeline results screen that links to config screen of classic
          * Add a cog to pipeline summary screen in the case of multibranch linking to classic
          * In the case of a github organization created job, the cog should link to the config for the org in classic (which is the only real config page)

           !Screen Shot 2016-10-28 at 1.19.05 pm.png|thumbnail! !Screen Shot 2016-10-28 at 1.19.24 pm.png|thumbnail!


          When clicking on the cog, for example on the multibranch project called "keitha", it should link to something like this:

           !Screen Shot 2016-10-31 at 9.52.58 am.png|thumbnail!

          (the uri pattern is predictable, so should be easy).
          Increasingly there have been demands to have a link to equivalent classic pages, specifically around config. There are designs for this that use a "cog" icon.

          These can link to the config screen in classic until there is an equivalent config screen for blue ocean.

          In scope:
          * Add a cog to pipeline results screen that links to config screen of classic
          * Add a cog to pipeline summary screen in the case of multibranch linking to classic
          * In the case of a github organization created job, the cog should link to the config for the org in classic (which is the only real config page)
          * Cog should open config screen in new browser tab

           !Screen Shot 2016-10-28 at 1.19.05 pm.png|thumbnail! !Screen Shot 2016-10-28 at 1.19.24 pm.png|thumbnail!


          When clicking on the cog, for example on the multibranch project called "keitha", it should link to something like this:

           !Screen Shot 2016-10-31 at 9.52.58 am.png|thumbnail!

          (the uri pattern is predictable, so should be easy).
          jamesdumay James Dumay made changes -
          Assignee Ivan Meredith [ imeredith ]
          jamesdumay James Dumay made changes -
          Rank Ranked higher
          tfennelly Tom FENNELLY made changes -
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Resolved [ 5 ]

            People

            Assignee:
            imeredith Ivan Meredith
            Reporter:
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: