-
Story
-
Resolution: Fixed
-
Critical
-
-
arctic
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).
[JENKINS-39338] Pipeline config "cog" to link to classic config screen
| Epic Link | New: JENKINS-35761 [ 171656 ] |
| Labels | New: adoption |
| Sprint | New: arctic [ 131 ] |
| Attachment | New: Screen Shot 2016-10-31 at 9.52.58 am.png [ 34643 ] |
| Description |
Original:
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! |
New:
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). |
| Description |
Original:
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). |
New:
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). |
| Assignee | New: Ivan Meredith [ imeredith ] |
| Rank | New: Ranked higher |
jamesdumay perhaps a quick win that can be scheduled earlier?